It's getting more and more important to be able to detect XO hardware
from userspace. One can no longer assume that Sugar implies XO because
Sugar runs elsewhere and because non-Sugar is getting common on the XO.
Considering the 1.5 hardware, assuming that Geode implies XO is not
going to be
On Fri, Jul 10, 2009 at 8:50 PM, Albert Cahalanacaha...@gmail.com wrote:
It's getting more and more important to be able to detect XO hardware
from userspace. One can no longer assume that Sugar implies XO because
Sugar runs elsewhere and because non-Sugar is getting common on the XO.
On Fri, Jul 10, 2009 at 11:20 AM, Albert Cahalanacaha...@gmail.com wrote:
It's getting more and more important to be able to detect XO hardware
from userspace. One can no longer assume that Sugar implies XO because
Sugar runs elsewhere and because non-Sugar is getting common on the XO.
On Fri, 2009-07-10 at 11:20 -0400, Albert Cahalan wrote:
It's getting more and more important to be able to detect XO hardware
from userspace. One can no longer assume that Sugar implies XO because
Sugar runs elsewhere and because non-Sugar is getting common on the XO.
Considering the 1.5
2009/7/10 Sayamindu Dasgupta sayami...@gmail.com:
You can probably poke HAL.
http://pastebin.be/19650 will give you the vendor name (which should be OLPC).
Be careful. In current builds, that only works for XOs with ALPS
touchpads. This will be fixed as we move to DMI-based detection.
Daniel
On Fri, Jul 10, 2009 at 4:10 PM, Walter Benderwalter.ben...@gmail.com wrote:
On Fri, Jul 10, 2009 at 11:20 AM, Albert Cahalanacaha...@gmail.com wrote:
I suppose the real needs are:
1. detect that the screen has XO-like blur
2. detect that the keyboard has XO-style keys
2a. detect that there
