[haiku-development] Re: Configuring device resources (IRQ/Memory).
- From: richard jasmin <jasminr@xxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 12 Aug 2008 15:47:07 -0400
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
agreed. most base hardware should be fine. okay, the mobo controllers
vary a little, but the default instruction set should work at least.Most
boards still have IDE connections still.most video cards still have VESA
modes. sound, well, its a ALC codec mostly nowadays, used to be SB16 or
compatible. NET has changed a lot since the rtl 8192 and similar
days.most computers can still get by with these specs, though. Lacking
drivers, not from what I saw. maybe R5 has a lack, but ZETA didn't seem to.
can't you pull those from kernel.org's kernel source tree? <-- just a guess.
i think ACPI is more implemented nowadays.the combined tree i think was
windows and Linux standards since the invention of a 'control panel'.it
goes back beyond R-HAT days, but is there.
- ---
Bruno Albuquerque wrote:
> Right now it seems we completely rely on the configuration done by the
> BIOS and do not try to configure devices at all. This is a problem
> because the BIOS not always do a good job at configuring devices ans, in
> some cases (and I just hit this), devices show up after the BIOS
> finished configuring everything (see JMicron split function controllers).
>
> At some point there was some talk about using ACPI to configure the
> system but it seems this did not really progress so I would like to
> re-open the discussion as I think if we want to do a public release,
> even if an alpha, it would be good to at least have the basic system
> configuration working, even if we lack drivers for most of the devices
> around. :)
>
> At this point we do have a complete implementation of ACPI in our tree.
> What would it take to get this working for configuring devices? Maybe we
> should enumerate all devices via ACPI instead of PCI? Or just provide a
> combined device tree through device manager?
>
> Any other opinions about this?
>
> -Bruno
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIoei6ZWyv5fvyGz0RAppFAJ9lvVLxYcTTbh4Y2DCxAitmoDsXuQCfadmT
l4SQodB4c9/CdLZQY07srZU=
=CZd5
-----END PGP SIGNATURE-----
Other related posts:
