identifying a 1.75
Paul Fox
pgf at laptop.org
Wed Aug 10 12:27:06 EDT 2011
martin wrote:
> On Tue, Aug 9, 2011 at 6:31 PM, Paul Fox <pgf at laptop.org> wrote:
> > thoughts/comments? better approaches? obvious additions?
>
> Hi Paul
>
> timely - I was just hacking on olpc-utils, bitfrost and sugar on
> exactly the same thing (while on the plane, no internet).
>
> Something along the lines of what you have is needed, I'll probably
> merge it into my hacking. And we need it as part of a mini bash
> function library as well, machine identification and other tasks
> reading from ofw are spread across olpc-utils at random.
>
> So I'll prolly hack olpc-hwinfo into a shell of what you posted (oh!
> the pun!) -- calling into shared function calls. And will refactor
> other scripts to match.
something else i found this morning, while looking at #11126 -- udev
uses dmi/id/product_name to decide to apply our keyboard map. this
won't work on 1.75, so i guess we'll need to choose a/the canonical
method of distinguishing a 1.75 from sysfs.
paul
>
> cheers,
>
>
>
> m
> --
> martin.langhoff at gmail.com
> martin at laptop.org -- Software Architect - OLPC
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
=---------------------
paul fox, pgf at laptop.org
More information about the Devel
mailing list