linux-kernel - Re: Kernel for olpc-1.75

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20140609110518.GB25705@amd.pavel.ucw.cz>
Date:	Mon, 9 Jun 2014 13:05:18 +0200
From:	Pavel Machek <pavel@....cz>
To:	Daniel Drake <dsd@...top.org>
Cc:	kernel list <linux-kernel@...r.kernel.org>, chris@...ntf.net,
	dsd@...too.org
Subject: Re: Kernel for olpc-1.75

Hi!

> On Sat, Jun 7, 2014 at 11:53 PM, Pavel Machek <pavel@....cz> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/