Hi Stephen, On Mon, Dec 12, 2011 at 10:31 AM, Stephen Warren <swar...@nvidia.com> wrote: > On 12/12/2011 11:10 AM, Simon Glass wrote: >> On Mon, Dec 12, 2011 at 10:00 AM, Stephen Warren <swar...@nvidia.com> wrote: >>> On 12/08/2011 02:56 PM, Simon Glass wrote: > ... >>> I'd like to ask for comments in linux-input in case they have any other >>> ideas, e.g. whether a set of separately documented modifier mapping >>> properties makes sense. If not, I suppose the following set of >>> properties would suffice: >>> >>> nvidia,keycode-plain >>> nvidia,keycode-fn >>> u-boot,keycode-shift >>> u-boot,keycode-ctrl >>> >>> (although the last two seem to want both nvidia, and u-boot, prefixes) >> >> OK. Since this seems to be a kernel issue and Nvidia-specific can I >> ask if you can please send this email? I will wait for confirmation >> that this is OK before going further. > > OK, I'll send the email.
Thanks. > > I would like to point out though that this is neither a kernel issue nor > NVIDIA-specific: It's a device tree issue dealing with how to best > represent certain HW features, and it will apply equally to any HW that > has a keyboard with modifier keys; essentially all of them. Sorry I don't quite understand what you mean by that, given your comments that we should ask on linux-input. While it could apply to the two existing keyboard drivers, they each do their own thing at present. Regards, Simon > > -- > nvpublic _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot