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

[CIJOML <cijoml@volny.cz>]

Dne čt 22. února 2007 Dmitry Torokhov napsal(a):
> On 2/21/07, CIJOML <cijoml@volny.cz> wrote:
> > 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.
>
> They can get vendor and id from /proc/input/devices as well. Plus I
> will export uniq in /proc/bus/input/devices and then yo can ask X guys
> to allow matching on uniq as well.

Hi Dmitri,

I watched at 2.6.23 and this is still not done yet. Are there any patches 
available to use???

Thanks a lot for reply

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