On Tue, 15 May 2001, Jeff Garzik wrote:
> Linus Torvalds wrote:
> > Now, if we just fundamentally try to think about any device as being
> > hot-pluggable, you realize that things like "which PCI slot is this device
> > in" are completely _worthless_ as device identification, because they
> > fundamentally take the wrong approach, and they don't fit the generic
> > approach at all.
>
> Should I interpret this as you disagreeing with
> exporting-bus-info-to-userspace type additions? ie. some random
> get-info ioctl spits out pci_dev->slot_name to userspace.
>
> I believe there are rare cases where this is useful. When one already
> has the /dev node (via an open fd used for ioctl, usually), additionally
> you need the bus info to make an association between an active device on
> the hardware bus, and an active driver in the kernel. X could use this
> info to figure out which fbdev devices to avoid. SCSI is already using
> similar info, as of 2.4.4, as are net devs. Userspace apps that diddle
> hardware are a definite minority case, but for that case the PCI slot
> info is useful.
X can already look at the fb_fix_screeninfo.{smem,mmio}_start fields and match
that with pci_dev.resource[*].
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [EMAIL PROTECTED]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
