deepak wrote:
On Sep 15 2009, at 17:31, Paul Fox was caught saying:
john wrote:
there's no SysRq key on the XO keyboard, so you'll need to use a
break on the serial console to invoke it...
Please. If you're going to put this hook in, which I think is a great
idea,
On Thu, Sep 17, 2009 at 05:10:06AM -0400, Paul Fox wrote:
but the issue is that there's no such key on the XO keyboard: SysRq/PrtSc
doesn't exist.
Key to the left of frame and above erase is still free isn't it? ;-)
The legend matches my idea of switching to OFW. Another system hiding
in
On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
Why? Security reasons?
Martin
Martin Dengler wrote:
On Wed, Sep 16, 2009 at 11:18:17AM +0800, Mitch Bradley wrote:
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
Another objection, now that I think about it, is that some people didn't
like the way I made OFW coexist within Linux's virtual address space by
injecting a page directory entry at the top of one of Linux's page
tables. Admittedly, the solution that I chose is rather brute force,
but
it sounded like there was also some thought that the emphasis
should be on tools, like kgdb, which can be more general purpose,
and more widely used and maintained. to which i'd say, the more
the merrier -- i'd love to use kgdb regularly, but it requires a
second machine, and it ties up
On Tue, Sep 15, 2009 at 7:42 AM, Paul Fox p...@laptop.org wrote:
on the XO, openfirmware stays resident when linux runs, and is
accessible via an API specified in arch/x86/kernel/ofw.c. i've
just pushed a commit to our 2.6.30 kernel branch that adds a
sysrq hook (SysRq-y) for starting
on the XO, openfirmware stays resident when linux runs, and is
accessible via an API specified in arch/x86/kernel/ofw.c. i've
just pushed a commit to our 2.6.30 kernel branch that adds a
sysrq hook (SysRq-y) for starting (returning to?) the resident
OFW command line interface. when invoked, you
On Tue, Sep 15, 2009 at 10:42:46AM -0400, Paul Fox wrote:
on the XO, openfirmware stays resident when linux runs, and is
accessible via an API specified in arch/x86/kernel/ofw.c. i've
just pushed a commit to our 2.6.30 kernel branch that adds a
sysrq hook (SysRq-y) for starting (returning
martin wrote:
On Tue, Sep 15, 2009 at 10:42:46AM -0400, Paul Fox wrote:
on the XO, openfirmware stays resident when linux runs, and is
accessible via an API specified in arch/x86/kernel/ofw.c. i've
just pushed a commit to our 2.6.30 kernel branch that adds a
sysrq hook (SysRq-y) for
there's no SysRq key on the XO keyboard, so you'll need to use a
break on the serial console to invoke it...
Please. If you're going to put this hook in, which I think is a great
idea, at least make it work on the standard hardware! And when the
operating system is not very responsive.
On 15.09.2009, at 23:21, John Gilmore wrote:
there's no SysRq key on the XO keyboard, so you'll need to use a
break on the serial console to invoke it...
Please. If you're going to put this hook in, which I think is a great
idea, at least make it work on the standard hardware! And when
john wrote:
there's no SysRq key on the XO keyboard, so you'll need to use a
break on the serial console to invoke it...
Please. If you're going to put this hook in, which I think is a great
idea, at least make it work on the standard hardware! And when the
operating system is not
It is gratifying that so many people like the idea of being able to zap
back into OFW from Linux - especially since I got such intense pushback
when I first proposed leaving OFW resident on OLPC.
___
Devel mailing list
Devel@lists.laptop.org
14 matches
Mail list logo
