RE Suspend / Resume : talk to CJB(Chris Ball) about OHM. I spoke with him a few weeks ago and, if I recall correctly, all one needs to do is use the official OLPC Kernel and install the OHM packages.<br><br><div class="gmail_quote">
On Mon, Nov 3, 2008 at 1:20 AM, <span dir="ltr"><<a href="mailto:david@lang.hm">david@lang.hm</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Mon, 3 Nov 2008, James Cameron wrote:<br>
<br>
> On Sun, Nov 02, 2008 at 09:27:52PM -0800, <a href="mailto:david@lang.hm">david@lang.hm</a> wrote:<br>
>> On Mon, 3 Nov 2008, James Cameron wrote:<br>
>>> The TODO file in the xodist git repository has a hardware enablement<br>
>>> section that I added last week, which covers some of the things this<br>
>>> thread has discussed.<br>
>><br>
>> link to xodist please?<br>
><br>
> xodist is the git repository name for the scripts that generate debxo<br>
> images.<br>
<br>
</div>sorry, I missed that (and I even have that repository cloned, shame on me<br>
:-)<br>
<div class="Ih2E3d"><br>
> git://<a href="http://lunge.mit.edu/git/xodist" target="_blank">lunge.mit.edu/git/xodist</a> (per Andres' mail of 28th Oct)<br>
> or<br>
> <a href="http://dev.laptop.org/%7Equozl/xodist.git/" target="_blank">http://dev.laptop.org/~quozl/xodist.git/</a> (my repo, sync'ed)<br>
><br>
>> do you have the direction and rotate game keys working?<br>
><br>
> I don't know.<br>
<br>
</div>they do not in the 0.3 build<br>
<div class="Ih2E3d"><br>
>>> brightness control keys (conflicts with function key usage)<br>
>>> volume control keys (conflicts with function key usage)<br>
>><br>
>> these don't need system changes, just deciding which function those keys<br>
>> should do, the brightness and volume functions are strictly in software<br>
>> (and done via X hooks, as can be shown by the fact that these do not work<br>
>> in a console, and in fact crash the system if you hit them there)<br>
><br>
> Seems more logical to handle these keys in the kernel.<br>
<br>
</div>I don't think so. since the hardware produces the function keys, if the<br>
kernel does the functions instead of userspace, you loose the flexibility<br>
to use these as normal function keys.<br>
<br>
the tendancy is to push more of this sort of thing to userspace anyway.<br>
the volume keys onthe thinkpads recently changed from being handled by the<br>
hardware to be intercepted by the kernel and treated as normal keys (with<br>
the default bindings being to control the volume) a few months ago this<br>
worked in Gnome, but not KDE, with the ubuntu release a few days ago it<br>
works in both (I don't use sound enough to have tried it outside of X)<br>
<div class="Ih2E3d"><br>
>>> turn off backlight on suspend or hibernate<br>
>><br>
>> I don't use suspend or hibernate enough to help, but now that we have the<br>
>> script to control the backlight this should be fairly easy (although you<br>
>> really want to turn off the entire screen, not just the backlight, at<br>
>> least for hibernate, don't you?)<br>
><br>
> If you're saying "the OLPC XO build also turns off the screen hardware",<br>
> then the next question is "how?" ... presumably this can be found by<br>
> examining it.<br>
<br>
</div>the thought just hit me that we don't always want to turn off the screen<br>
on suspend, unlike normal systems the XO is designed to be able to run the<br>
display when the main processor is suspended (although I remember being<br>
told that this isn't working due to software limitations today)<br>
<div class="Ih2E3d"><br>
>>> The latter method is how xodist's initchroot.sh script does some<br>
>>> features ... like setting up /etc/modules, xorg.conf, and so forth.<br>
>><br>
>> I'm actually not happy with how the OLPC currently handles these things,<br>
>> they are too X (and sugar) specific. we need to get a layer lower if we<br>
>> can.<br>
><br>
> Good. But the general purpose solutions in Debian are perhaps too<br>
> general for this situation. Things like the discover package.<br>
<br>
</div>ideally I want to figure out how to get these keys into the kernel, at<br>
that point any userspace can deal with them.<br>
<br>
David Lang<br>
<div><div></div><div class="Wj3C7c">_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ian Daniher<br>--<br>OLPC Support Volunteer<br>OLPCinci Repair Center Coordinator<br>--<br><a href="mailto:it.daniher@gmail.com">it.daniher@gmail.com</a><br>Skype : it.daniher<br>
<a href="http://irc.freenode.net">irc.freenode.net</a>: Ian_Daniher<br>--<br>c: 513.290.4942<br>