Hi,
I think you may want to look at the boot code and dig around a bit. Here's what I know.
In sys/boot, there's a lot of code already that makes up the loader. As the loader used to be able to boot an ia64 aka Itanium which exclusively has EFI and no BIOS, there's some EFI code available...
Once the operating system is up and running, you really don't want any interaction with the platform firmware for performance reasons. However, there are certain functions that rely on firmware, e.g. rebooting or powering off a system. I think on i386/amd64 this is abstracted through ACPI which...
As far as I know, the FreeBSD kernel does rely on some BIOS calls during the early boot phase. The standard i386/amd64 loader certainly needs a BIOS, even though there apparently is an EFI version of it.
So after digging through the bus and PCI code, it seems the generic PCI-ISA driver (isab) has allocated the resources. It does that because the device announces itself as a PCI-ISA bridge and claims certain memory and I/O resources in its BARs. Further, the PCI code will only assign resources to...
Hi,
I have an Alix 1.C for which I'm trying to write an I2C device driver. The system is AMD Geode LX based and as such has an AMD CS5536 South Bridge that contains the I2C/SMBus hardware. Judging by the datasheet available at http://support.amd.com/us/Embedded_TechDocs/33238G_cs5536_db.pdf...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.