tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: basic support for (software concept) "pci domains" in the MI pci code
On Mon, Aug 24, 2009 at 11:03:52PM +1000, Simon Burge wrote:
> matthew green wrote:
>
> > there's still a story to solve wrt /dev/pci* nodes. we only create
> > upto /dev/pci7 and that isn't enough, and this is probably what is
> > driving cegger's problem.
>
> Without really thinking, is this a problem? Consider that:
>
> pcictl pci0 list -b 2
> pcictl pci2 list
>
> given the same output and the first opens /dev/pci0 and the second opens
> /dev/pci2. I don't know how these are routed in the kernel, so don't
> know if any arbitary "pciN" is the equivalent to "pci0 -b N"...
It's not. You happen to have pci2 as pci bus number 2 on your system.
On my alpha:
armandeche:/local/armandeche1/bouyer>pcictl pci0 list -b1
[nothing]
armandeche:/local/armandeche1/bouyer>pcictl pci1 list
000:03:0: Digital Equipment DC21142/21143 10/100 Ethernet (ethernet network,
revision 0x41)
000:08:0: Digital Equipment DC21152 PCI-PCI Bridge (PCI bridge, revision 0x03)
But we don't really need '-b' ...
--
Manuel Bouyer <bouyer%antioche.eu.org@localhost>
NetBSD: 26 ans d'experience feront toujours la difference
--
Home |
Main Index |
Thread Index |
Old Index