On Mon, 2009-11-23 at 11:37 -0500, Paul Fox wrote:
> on the XO, setkeycodes doesn't seem to be able to remap some
> keys correctly. in particular, i tried to use the "Zoom" and
> "Divide/Multiply" keys, to no avail.
This is probably because we've already remapped those keys using the
i wrote:
> 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
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 t
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
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, at least make i
On Tue, Sep 15, 2009 at 7:42 AM, 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 to?) the
> 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
mitch wrote:
> 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
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 empirical
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
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
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
http://lis
On Tue, 15 Sep 2009, John Gilmore wrote:
> Date: Tue, 15 Sep 2009 14:21:14 -0700
> From: John Gilmore
> To: Paul Fox
> Cc: devel@lists.laptop.org
> Subject: Re: OFW access from linux
>
>> there's no SysRq key on the XO keyboard, so you'll need to use a
>&g
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
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 w
> 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. That
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 (SysR
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
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 c
19 matches
Mail list logo
