From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933327AbaFILFW (ORCPT ); Mon, 9 Jun 2014 07:05:22 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:46220 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932253AbaFILFU (ORCPT ); Mon, 9 Jun 2014 07:05:20 -0400 Date: Mon, 9 Jun 2014 13:05:18 +0200 From: Pavel Machek To: Daniel Drake Cc: kernel list , chris@printf.net, dsd@gentoo.org Subject: Re: Kernel for olpc-1.75 Message-ID: <20140609110518.GB25705@amd.pavel.ucw.cz> References: <20140607225356.GA5696@amd.pavel.ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! > On Sat, Jun 7, 2014 at 11:53 PM, Pavel Machek wrote: > > I broke installation on olpc-1.75, and I guess its time for it to > > start running self-compiled kernel. (It still boots if I hold right > > game key, but I can no longer control backlight. It does not boot at > > all by default.) > > > > AFAICT, olpc.fth and zImage in the boot/ directory of USB disk should > > do the trick. > > > > Unfortunately, 3.0 based kernels no longer compile with current tools, > > so I tried this version (3.6 based). > > Sorry but OLPC never progressed beyond shipping 3.0 on this hardware, > and low-level development only really happens in maintenance mode at > the moment. :-(. > We did almost get a newer version working, but it had some unresolved > issues that prevented us from shipping it to users. I'm not sure of > the state of that arm-3.6 branch you are trying but I don't see > anything wrong in your process. I would try early printascii() calls > and a serial cable next. Ok, that's more debugging than I can do at the moment, given my inexperience with this hardware. I guess I should really try arm-3.0 branch... > Mainline won't run on the machine in any kind of usable state without > quite a bit of work on drivers and DT (which comes from the firmware). > I did once start on that but didn't manage to get even the initial > easy patches past the Marvell maintainers :( Hmm, that's sad... but perhaps Marvell maintainers improved in the meantime? Would you have working zImage binary I could use for experiments? Thanks, Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html