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. Regards Marcel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
