On Thu, Jun 01, 2000 at 01:23:25AM -0400, Jeff Garzik wrote:
> "David S. Miller" wrote:
> > Why not just make the eepro100 driver print out it's bus/devfn
> > PCI geography, and then you have "eth%d" and the PCI bits
> > to do your groveling with.
>
> This reminds me of an old topic from linux-fbdev -- the X server needs
> to know the fbdev device's bus/slot/devfn info, so that it may skip it
> when doing its own h/w probe. The current hueristic, as you yourself
> pointed out :), is inadequate for 32-bit buses on 64-bit machines.
>
> Attached is Jakub Jelinek's proposal. I agree w/ him - the concept of
> being able to report to userspace a device's bus info is very useful for
> many situations, including fbdev and $subject.
The issue why is this not implemented yet is:
Linus did not like the idea of one struct hwdevice which would be a union of
struct pci_dev, struct sbus_dev and whatever other buses where the first
field in all the structs would be bus id.
The end of that discussion (at least I think) that we'll use struct pci_dev
and its private fields for sbus device structs and other buses will do the
same and finally struct pci_dev will be renamed to struct hw_dev or whatever
(with pci_dev as valid type for backward compatibility).
The problem is that we have not done this yet...
Jakub
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Jun 07 2000 - 21:00:11 EST