16 messages in org.freebsd.freebsd-hackersHow disable attachment of sio(4) driv...| From | Sent On | Attachments |
|---|---|---|
| Frank Behrens | Oct 21, 2005 1:36 am | |
| M. Warner Losh | Oct 21, 2005 9:07 am | |
| John Baldwin | Oct 21, 2005 9:37 am | |
| M. Warner Losh | Oct 21, 2005 10:36 am | |
| Marcel Moolenaar | Oct 21, 2005 12:10 pm | |
| Bernd Walter | Oct 21, 2005 1:39 pm | |
| Daniel O'Connor | Oct 21, 2005 11:31 pm | |
| Bernd Walter | Oct 22, 2005 5:18 am | |
| Daniel O'Connor | Oct 22, 2005 6:00 am | |
| Frank Behrens | Oct 22, 2005 8:17 am | |
| Frank Behrens | Oct 22, 2005 8:17 am | |
| M. Warner Losh | Oct 22, 2005 9:33 am | |
| Bernd Walter | Oct 24, 2005 5:32 am | |
| Frank Behrens | Oct 24, 2005 5:46 am | |
| John Baldwin | Oct 24, 2005 8:42 am | |
| M. Warner Losh | Oct 24, 2005 9:27 am |
| Subject: | How disable attachment of sio(4) driver to device? | |
|---|---|---|
| From: | M. Warner Losh (im...@bsdimp.com) | |
| Date: | Oct 21, 2005 10:36:43 am | |
| List: | org.freebsd.freebsd-hackers | |
In message: <2005...@freebsd.org> John Baldwin <jh...@FreeBSD.ORG> writes: : But you could hack the sio(4) driver to check its IO port and return ENXIO if : it has a certain value, for example.
Yes. You could also do that. I have a tree somewhere that has some changes in this direction, but I was unsatisified with it. I set out to solve the 'I want SIO0 to be defined as PORT_B, since that's the only one my server exports via acpi, how the heck do I know what adress it is at, really?' problem too.
devinfo says:
sio0 pnpinfo _HID=PNP0501 _UID=1 at handle=\_SB_.PCI0.PX40.UAR1 sio1 pnpinfo _HID=PNP0501 _UID=2 at handle=\_SB_.PCI0.PX40.UAR2
I'd like to be able to say that sio0 is at handle=\_SB_.PCI0.PX40.UAR2 rather than some arbitrary address. Or that bge1 is at
bge0 pnpinfo vendor=0x14e4 device=0x16a6 subvendor=0x14e4
subdevice=0x8009 class=0x020000 at slot=3 function=0 handle=\_SB_.PCI0.G0PA.LAN0
miibus0
brgphy0 pnpinfo oui=0x818 model=0x16 rev=0x2 at phyno=1
bge1 pnpinfo vendor=0x14e4 device=0x16a6 subvendor=0x14e4
subdevice=0x8009 class=0x020000 at slot=4 function=0 handle=\_SB_.PCI0.G0PA.LAN1
either at pci2.4.0 *OR* at handle=\_SB_.PCI0.G0PA.LAN1 (or even handle=LAN1). So there'd need to be some kind of bus specific mapping function that would say true or false if a given device_t on that bus matched the string presented.
You could then say that the device at handle=UAR1 belongs to mydev3, and sio would never even be given a chance to bid on it.
I'm not sure how to work this into the current hints paradigm...
Warner