You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Robin Smidsrød df202b3f4d [build] Avoid using embedded script in VirtualBox named configuration 9 年之前
..
README [build] Avoid using embedded script in VirtualBox named configuration 9 年之前
colour.h [build] Add named configuration for VirtualBox 10 年之前
console.h [build] Add named configuration for VirtualBox 10 年之前
crypto.h [build] Add named configuration for VirtualBox 10 年之前
general.h [build] Avoid using embedded script in VirtualBox named configuration 9 年之前
serial.h [build] Add named configuration for VirtualBox 10 年之前
settings.h [build] Add named configuration for VirtualBox 10 年之前
sideband.h [build] Add named configuration for VirtualBox 10 年之前

README

Build using this command line:

make CONFIG=vbox bin/intel--virtio-net--pcnet32.isarom

Max size of a VirtualBox ROM is 56KB, 57344 bytes. There should be no need
to pad the image as long as the binary is smaller or equal to this size.

To use the ROM in VirtualBox you need to enable it using this command:

vboxmanage setextradata global \
VBoxInternal/Devices/pcbios/0/Config/LanBootRom \
/absolute/path/to/intel--virtio-net--pcnet32.isarom

NB: If you build the ROM using the .rom prefix then it'll be built as a PCI
ROM, which won't work properly in VirtualBox. The error message you'll see
is "No more network devices", which is somewhat confusing. If you enter the
shell and use the "autoboot" command things will work as intended. Remember
to always build as a .isarom to avoid this issue.