Sylvain Munaut <[email protected]> wrote on 15.02.2007 15:11:42:
> Mmmh, I posted a patch that added a common uevent interface for all
> of_device based bus. And that kinda clash with this one.
Oops, I was not aware of this. I had a look at your patch and yes, it's a
nice
and generic interface. I concur that using your generic function is the
better
approach.
> But as "ibm,loc_code" is local to this bus it's not handled by my code.
> Is it necessary to match the correct driver ?
The intention of adding the location code was to include a device property
into the environment that's unique to each device. Actually, the DEVPATH
variable
provides exactly this: For ebus devices, it points to the ebus device
itself,
which natually is unique.
If a userspace tool really needs the location code, the "devspec"
attribute of
the ebus device will point it to the device tree node, which in turn
contains the
location code property.
So I think there's nothing preventing me from using your function. Thanks
for
pointing this out.
Regards,
Joachim
---
Joachim Fenkes -- eHCA Linux Driver Developer and Hardware Tamer
extraordinaire
IBM Deutschland Entwicklung GmbH -- Dept. 3627 (I/O Firmware Development
2)
Schoenaicher Strasse 220 -- 71032 Boeblingen -- Germany
eMail: [email protected] -- Phone: +49 7031 16 1239
Vorsitzender des Aufsichtsrats: Johann Weihen -- Geschäftsführung:
Herbert Kircher
Sitz der Gesellschaft: Böblingen -- Registergericht: Amtsgericht
Stuttgart, HRB 243294
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
