| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <1172098430.7403.54.camel@violet> Date: Wed, 21 Feb 2007 23:53:50 +0100 From: Marcel Holtmann <marcel@...tmann.org> To: Dmitry Torokhov <dmitry.torokhov@...il.com> Cc: CIJOML <cijoml@...ny.cz>, linux-kernel@...r.kernel.org Subject: Re: Re: Phis in /proc/bus/input/devices same for all devices? 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. Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists