Re: [RFC] fix sysfs symlinks

[Russell King]

On Fri, Apr 16, 2004 at 08:03:50PM -0400, Jeff Garzik wrote:
> Ideally one would think that userland can deduce relationships by 
> looking at the attribute information sysfs already provides -- and if 
> not, it's just one more bit of info to export via sysfs.

They can?  So, does userspace need to know the PCI IDs associated
with each driver so it can match the devices?  Without the symlinks
in /sys/bus/foo/devices, how do we know which devices are PCI devices
and which aren't?  etc...

Sure you can say "well, this device seems to have a this that and the
other attribute, which appears to match what we think a PCI device
should have" but then you're assuming that group of attributes only
appears for PCI devices.

What about other bus types?  Do I really need to teach userspace about
the relationships between all the various bus types we have on ARM and
how to work out what these relationships are by guessing?

Please.  The symlinks are necessary and they are the sole source of
the relationship information.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/