karl o. pinc wrote: > On 08/16/2011 05:54:04 PM, Daniel Drake wrote: > > > However, to complicate things further with another item on our TODO > > list: OLPC offers the same identical laptop models with two alternate > > keyboards - membrane and mechanical. This is for both x86 and ARM > > models. At the moment, we use the same keymap for both even despite > > differences in the keys, but we plan to improve on this in future > > since it is a bug that keys do not behave according to the symbols > > printed on them! > > > > There is no other difference in the laptop other than the keyboard, > > so > > this information could not be captured in the bare-bones info > > presented in DMI or by the theoretical system mentioned above, unless > > we were to do something hacky like encode the keyboard model in the > > product_name. > > I don't understand. > > Why is it a hack to encode the keyboard model in the product name? > When the keyboard is part of the product and there's two different > keyboards (not just mechanically, but with different keymaps) > why isn't it 2 product models? we have three laptop models, and something like 20 different keyboards. whether or not they all need different keymaps (they don't), i think you can see why we might not necessarily encode any of them as different models. paul =--------------------- paul fox, pgf@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
