hi --
OLPC's latest laptop (the 1.75 model) is ARM-based. this means the
current keymap rule in rules.d/95-keymap.rules:
ENV{DMI_VENDOR}=="OLPC", ATTR{[dmi/id]product_name}=="XO", \
RUN+="keymap $name olpc-xo"
won't trigger -- there's no DMI information.
any thoughts on how non-PC hardware should be identifying itself
to udev? are there other examples of how this might be done?
i'm sure we could come up with something, based on examining some
other sysfs attribute, or perhaps running a command which identifies
our laptop(s), but i suspect this issue has come up before.
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
