Messages in this thread | | | Date | Thu, 22 Feb 2007 10:06:09 -0500 | From | "Dmitry Torokhov" <> | Subject | Re: Re: Phis in /proc/bus/input/devices same for all devices? |
| |
Hi Marcel,
On 2/21/07, Marcel Holtmann <marcel@holtmann.org> wrote: > Hi Dmitry, > > > > > > can anybody reply to this and share his/her opinion? > > > > > > > > Input core already exports uniq to udev and also via sysfs. > > > > > > so do you think it would be better to create phys as a string of the > > > source and destination address like "<src>-<dst>" for Bluetooth. And > > > then keep the uniq empty like all USB devices without serial number do? > > > > > > > I'd keep uniq as is and do what you proposed with phys. This way you > > can either use uniq to identify your device while moving it from one > > receiver to another (if you have several) or do exact match on phys to > > get receiver/device pair. > > > > Does this make sense? > > actually it doesn't help to keep uniq around since the Bluetooth HID > always reconnects to the same source/host address. Making it reconnect > results in a virtual cable unplug. So I think that I am going to modify > the phys to include source and destination address. In the end it is > only a string. >
Matching on uniq (and having uniq available) makes sense when you want to perform device-specific setup and want it to work even if you change your BT adapter. Imagne yopu have a keyboard that yoou want to handle in a special way and after you set up your BT card gets fried and you buy another one. When matchign on uniq your setup will not change at all.
-- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |