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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 22 Feb 2007 00:02:19 +0100
From:	CIJOML <cijoml@...ny.cz>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Phis in /proc/bus/input/devices same for all devices?

Dne čtvrtek 22 únor 2007 00:00 Marcel Holtmann napsal(a):
> Hi Michal,
>
> > 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.
>
> it makes sense to make it analogous to the USB driver, where the phys
> includes the USB path. The equivalent for Bluetooth is the source plus
> destination.
>
> > 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
>
> I don't know how "Phis" suppose to work, but I might think it is better
> using vendor and product ID for matching.

Xorg just reads lines from devices and match devices against it. So Phis makes 
configuration easier ;), because only one line is enough to match device.

>
> Regards
>
> Marcel

Michal
-
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ