Re: When will PCI_ENABLE_IO_MODES be default?
On Wed, Jul 17, 2002 at 23:33:13 -0600, M. Warner Losh wrote: It is a tiny piece of a larger puzzle that will be fixed as we do proper resource allocation now that the BIOS specifications have been changed by MS to move that into the OS. Can you elaborate on that or give some pointers? rvdp To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: When will PCI_ENABLE_IO_MODES be default?
In message: [EMAIL PROTECTED] Ronald van der Pol [EMAIL PROTECTED] writes: : On Wed, Jul 17, 2002 at 23:33:13 -0600, M. Warner Losh wrote: : : It is a tiny piece of a larger puzzle that will be fixed as we do : proper resource allocation now that the BIOS specifications have been : changed by MS to move that into the OS. : : Can you elaborate on that or give some pointers? Short answer: ACPI. :-) Longer Answer: For some time now MS has had the notion of a Plug and Play OS at the BIOS level. Most BIOSes had the ability to say This OS is a Plug and Play OS and would refrain from assigning resources to the pci cards that might be a pita for the PnP OS to deal with down the road. In a Plug and Play OS, it deals with resource issues compeletely and totally (except for devices required to boot the system, iirc). In a non PnP OS, like FreeBSD, the OS expects the BIOS to have assigned all the resources and activated all the cards. For years, this worked great. ACPI can be viewed as an even more extensive attempt to get the OS to assign all the resources to the cards. Now with ACPI in more and more BIOSes, they are shipping w/o the ability to turn off PnP OS. They assume that the OS will be at least PnP, if not fully use the ACPI paradigm[*] to do its resource thing. FreeBSD has to cope with this better in general. PCI_ENABLE_IO_MODES is a kludge that only kinda makes things better. NetBSD does a better job at this by enumerating things at boot time and assigning resources when the big picture is being looked at. FreeBSD should do this as well. We will have to deal with assigning things that could need more resources later, like cardbus and cPCI bridges, big chunks of space that they can later dole out as needed. pci bridges make this problem more interesting because some of them will only decode certain address ranges (which is the cause of another kludge in the pci code). You can do a web search for the pc99 design guide (and newer ones). They go into some of this. The ACPI standards docs also go into this as well, although the 1.0 verion didn't do it very well (imho). There are a number of other places to look for information too. The mindshare books might be good. I'm not aware of one place the ties all of these customs together into a coherent hole :-(. Warner [*] These are wesil words for The OS does all the resource assignment. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: When will PCI_ENABLE_IO_MODES be default?
So, how much does this have to do with my laptop's sound (DSP) dumping out after about 10 seconds? (Toshiba had the great idea of hard-wiring most everything through IRQ 11, although pccardd seems to be able to use others) Longer Answer: For some time now MS has had the notion of a Plug and Play OS at the BIOS level. Most BIOSes had the ability to say This OS is a Plug and Play OS and would refrain from assigning resources to the pci cards that might be a pita for the PnP OS to deal with down the road. In a Plug and Play OS, it deals with resource issues compeletely and totally (except for devices required to boot the system, iirc). In a non PnP OS, like FreeBSD, the OS expects the BIOS to have assigned all the resources and activated all the cards. For years, this worked great. ACPI can be viewed as an even more extensive attempt to get the OS to assign all the resources to the cards. Now with ACPI in more and more BIOSes, they are shipping w/o the ability to turn off PnP OS. They assume that the OS will be at least PnP, if not fully use the ACPI paradigm[*] to do its resource thing. FreeBSD has to cope with this better in general. PCI_ENABLE_IO_MODES is a kludge that only kinda makes things better. NetBSD does a better job at this by enumerating things at boot time and assigning resources when the big picture is being looked at. FreeBSD should do this as well. We will have to deal with assigning things that could need more resources later, like cardbus and cPCI bridges, big chunks of space that they can later dole out as needed. pci bridges make this problem more interesting because some of them will only decode certain address ranges (which is the cause of another kludge in the pci code). You can do a web search for the pc99 design guide (and newer ones). They go into some of this. The ACPI standards docs also go into this as well, although the 1.0 verion didn't do it very well (imho). There are a number of other places to look for information too. The mindshare books might be good. I'm not aware of one place the ties all of these customs together into a coherent hole :-(. Warner [*] These are wesil words for The OS does all the resource assignment. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
When will PCI_ENABLE_IO_MODES be default?
Hello, It seems like PCI_ENABLE_IO_MODES makes FreeBSD work on a lot of portable computers and possible newer desktop computers with lazy BIOS'es. As it is now, it is quite a hassle to complete something as simple as a network install of FreeBSD on an affected computer. My question is, when will PCI_ENABLE_IO_MODES be default? I know it will be by 5.0-RELEASE (hope?), but it would be nice to have it in there soon so people could install SNAPSHOT releases directly, or maby as a seperate disk-image if it makes some kind of trouble for other configurations. Having this in 5.0-DP2 would be nice ;) -- Mvh, Frode Nordahl To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: When will PCI_ENABLE_IO_MODES be default?
On Thu, Jul 18, 2002 at 12:58:55AM +0200, Frode Nordahl wrote: It seems like PCI_ENABLE_IO_MODES makes FreeBSD work on a lot of portable computers and possible newer desktop computers with lazy BIOS'es. As it is now, it is quite a hassle to complete something as simple as a network install of FreeBSD on an affected computer. My question is, when will PCI_ENABLE_IO_MODES be default? Probably never. :( While it fixes a number of devices on certain machines (including my current and previous laptop) it breaks other devices so we can't win. It should be possiable to make this tunable at boot time to remove the need for a kernel rebuild though. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 msg41172/pgp0.pgp Description: PGP signature
