Date: Sun, 05 Sep 1999 03:06:29 +0800 From: Peter Wemm <peter@netplex.com.au> To: Doug Rabson <dfr@nlsystems.com> Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, "Zach N. Heilig" <znh@thequest.net>, freebsd-current@FreeBSD.ORG Subject: Re: PNP ids missing in sio.c Message-ID: <19990904190629.898ED1CAA@overcee.netplex.com.au> In-Reply-To: Your message of "Sat, 04 Sep 1999 19:38:43 %2B0100." <Pine.BSF.4.10.9909041938120.2081-100000@salmon.nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Doug Rabson wrote:
> On Sat, 4 Sep 1999, John-Mark Gurney wrote:
>
> > Doug Rabson scribbled this message on Sep 4:
> > > > This is of course a special case, a cranky network card and a
> > > > non-compiling driver for it. If the new pnp code avoids using resource
s
> > > > hard-wired to non-pnp isa devices (it may, I changed hardware before th
e
> > > > code was fixed), there shouldn't be any problems. It was an excellent
> > > > excuse to boot that nic anyway.
> > >
> > > The trick for this is to make sure that the config file contains accurate
> > > descriptions of all your non-pnp hardware. In this case, if you have:
> > >
> > > device ed0 at isa? port 0x300 irq 5 ...
> > >
> > > then the subsequent pnp probes should avoid those port and irq settings.
> >
> > but the problem is that he couldn't have the line in because the driver
> > wouldn't compile... so are we going to add a dummy isa device that takes
> > up resources so that this won't happen again? maybe the user has some
> > win95 only isa card or something... but this needs to be able to be
> > configured... along w/ doing this at boot -c time too...
>
> We already have a dummy driver (unknown) which can be adapted for this
> purpose. Perhaps this is the best solution.
I'm curious what can be made of the PNP resource list we get from the BIOS
at boot time... It lists motherboard resources too, we could probably end
up with a fairly complete map of known resources to avoid.
dmesg from boot -v:
bios32: Found BIOS32 Service Directory header at 0xc00fd9e0
bios32: Entry = 0xfd9f0 (c00fd9f0) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xda11
pnpbios: Found PnP BIOS data at 0xc00fa020
pnpbios: Entry = f0000:a120 Rev = 1.0
pnpbios: 36624 devices, largest 247 bytes
pnpbios: handle 0 device ID PNP0000 (0000d041)
pnpbios: handle 1 device ID PNP0201 (0102d041)
pnpbios: handle 2 device ID PNP0100 (0001d041)
pnpbios: handle 3 device ID PNP0b00 (000bd041)
pnpbios: handle 4 device ID PNP0800 (0008d041)
pnpbios: handle 5 device ID PNP0c04 (040cd041)
pnpbios: handle 6 device ID PNP0303 (0303d041)
pnpbios: handle 7 device ID PNP0f13 (130fd041)
pnpbios: handle 8 device ID PNP0c01 (010cd041)
pnpbios: handle 9 device ID PNP0a03 (030ad041)
pnpbios: handle 10 device ID PNP0700 (0007d041)
pnpbios: handle 11 device ID PNP0401 (0104d041)
pnpbios: handle 12 device ID PNP0501 (0105d041)
pnpbios: handle 13 device ID PNP0501 (0105d041)
pnpbios: handle 14 device ID PNP0c02 (020cd041)
pnpbios: handle 15 device ID PNP0c02 (020cd041)
Other BIOS signatures found:
ACPI: 00000000
disk1s1a:> pnpscan -v
Probing PnP BIOS...
Probing ISA bus...
Probing PCI BIOS...
PNP scan summary:
PNP0000
PNP0201
PNP0100
PNP0b00
PNP0800
PNP0c04
PNP0303
PNP0f13
PNP0c01
PNP0a03
PNP0700
PNP0401
PNP0501
PNP0501
PNP0c02
PNP0c02
CSC0b36 : CS4236 Audio
0x80789004 : SCSI controller
0x70108086 : IDE controller
0x12298086 : Ethernet controller
0x70208086 : USB controller
I'm not sure if the boot time scan is supposed to see the Sound device as
well as the PCI devices or not.
pcm0: <CS4236> at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0
Cheers,
-Peter
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990904190629.898ED1CAA>