linux-kernel - Re: Phis in /proc/bus/input/devices same for all devices?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200702212354.38618.cijoml@volny.cz>
Date:	Wed, 21 Feb 2007 23:54:38 +0100
From:	CIJOML <cijoml@...ny.cz>
To:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
Cc:	"Marcel Holtmann" <marcel@...tmann.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Phis in /proc/bus/input/devices same for all devices?

I need this for differing Option "XkbModel" in Xorg, so I can bind to each
device it's model and has correct xev's scancodes based on model.
So I prefer to have as Phis just only BDADDR, because for me this doesn't make 
sense to have there device to which keyboard connect. Then I should have 1 
section for each receiver, which is stupid.

Section "InputDevice"
        Identifier  "Bluetooth Keyboard"
        Driver      "kbd"
        Option  "Name"  "Bluetooth HID Boot Protocol Device"
        Option  "Phis"        "BDADDR"
        Option      "XkbRules"  "xfree86"
        Option      "XkbModel"  "dinovo"
        Option      "XkbLayout" "us"
EndSection

and so on for every other BT keyboard I own.


Michal

Dne středa 21 únor 2007 23:48 Dmitry Torokhov napsal(a):
> On 2/21/07, Marcel Holtmann <marcel@...tmann.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?
-
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/