On Mon, 2007-12-31 at 18:10 +, David Woodhouse wrote:
An interesting goal would be cleaning up CONFIG_OLPC so that
it could be enabled in stock kernels of standard Linux distros.
I actually see that as a prerequisite for getting the thing upstream.
And the first step along that path
David Woodhouse wrote:
So here's an untested patch to make the reboot fixups slightly more
generic, so that we can easily add our own 'fixup' for the XO in a
fashion which will actually be mergeable upstream.
It would be slightly nicer and generic if we had
void (*mach_reboot_fixup)(void
On Sun, 2007-12-30 at 12:05 -1000, Mitch Bradley wrote:
I meant the OLPC kernel.
I presume that OLPC changes will be offered to mainline in some batch
fashion, rather than piecemeal. This particular one is of no upstream
value in isolation, as it is utterly dependent on OLPC-specific EC
David Woodhouse wrote:
As a general rule, that is totally incorrect. Changes should be pushed
towards upstream _before_ they're ever committed to our tree, and any
change which has been made only in the OLPC tree and not pushed upstream
should be considered volatile and likely to disappear...
On Mon, 2007-12-31 at 12:56 -0500, Bernardo Innocenti wrote:
btw, we still have code in /etc/init.d/olpc-configure that
tries to use one of those private ioctls to remap the leds,
and outputs errors if they're missing. Is this still needed?
Yes, I think so. And I think it probably even
1. Give One Get One: The G1G1 program ends on December 31. G1G1 has
not only made it possible to seed the launch of programs in Haiti,
Rwanda, Ethiopia, Cambodia, Mongolia, and Afghanistan, but we have
also greatly broaden the community of participation in the project.
The community has already
Richard noticed that on the community-development list there are at
least two reports of the EC going terminal, meaning that on boot
they get the error message: EC problem. Remove all power and
restart. We need to get those machines to Cambridge to investigate
further.
It is unlikely
On Dec 31, 2007 3:23 AM, Mitch Bradley [EMAIL PROTECTED] wrote:
resetting without the EC's knowledge. There is a 2-line patch in the
ticket; it makes the kernel reboot using the approved EC interaction.
Looking at your trac entry, I see:
The change is in arch/i386/kernel/reboot_fixups.c :
Mitch Bradley wrote:
Richard noticed that on the community-development list there are at
least two reports of the EC going terminal, meaning that on boot
they get the error message: EC problem. Remove all power and
restart. We need to get those machines to Cambridge to investigate
further.
Jaya Kumar wrote:
On Dec 31, 2007 3:23 AM, Mitch Bradley [EMAIL PROTECTED] wrote:
resetting without the EC's knowledge. There is a 2-line patch in the
ticket; it makes the kernel reboot using the approved EC interaction.
Looking at your trac entry, I see:
The change is in
Richard A. Smith wrote:
Mitch Bradley wrote:
Richard noticed that on the community-development list there are at
least two reports of the EC going terminal, meaning that on boot
they get the error message: EC problem. Remove all power and
restart. We need to get those machines to Cambridge
11 matches
Mail list logo
