OpenFirmware and Linux v5.0 on XO-1.75

[James Cameron]

On Sun, Apr 21, 2019 at 12:02:56PM +0200, Lubomir Rintel wrote:
> On Sat, 2019-04-20 at 18:08 +1000, James Cameron wrote:
> > On Fri, Apr 19, 2019 at 08:58:15AM +0200, Lubomir Rintel wrote:
> > > On Mon, 2019-02-25 at 20:00 +1100, James Cameron wrote:
> > > > On Sat, Feb 23, 2019 at 06:06:56PM +0100, Lubomir Rintel wrote:
> > > > > On Sat, 2019-02-23 at 10:52 +1100, James Cameron wrote:
> > > > > > On Fri, Feb 22, 2019 at 12:14:00PM +0100, Lubomir Rintel wrote:
> > > > > > > Also, which config? Mine is basically this:
> > > > > > > https://raw.githubusercontent.com/hackerspace/olpc-xo175-linux/lr/olpc-xo175/arch/arm/configs/olpc_xo175_defconfig
> > > > > > 
> > > > > > The config used by Fedora.
> > > > > > 
> > > > > > Can we work toward some kind of reproducible build?
> > > > > 
> > > > > Not sure what you mean here.
> > > > 
> > > > Sorry.  Configuring and building kernels is for me a rare thing to do,
> > > > and whenever I try I'm usually interrupted by something more urgent,
> > > > as I've quite a few other things I've got to do.  I'm still a newbie
> > > > at it because I can't dedicate the time.  [...]
> > > 
> > > So, over the last week or so, I spent some effort making this work with
> > > the OLPC RPM build tooling. Here's what I came up with:
> > > 
> > > http://v3.sk/~lkundrak/olpc/green_ears.jpeg
> > > [...]
> > > Firmware:
> > > 
> > >   git pull https://github.com/lkundrak/openfirmware/ lr/olpc-xo175-3
> > > 
> > > A couple more small fixups here and there since lr/olpc-xo175-2. The
> > > most notable fix is for a regression that caused the RTC to be cleared
> > > on each boot.
> > 
> > Pushed as
> > https://github.com/quozl/openfirmware/commits/lr/olpc-xo175-3
> > 
> > Released q4e00ja.rom from this as is;
> > http://dev.laptop.org/~quozl/q4e00ja.rom
> > 
> > Removed the dtcompat.fth fload and released q4e01ja.rom;
> > http://dev.laptop.org/~quozl/q4e01ja.rom
> 
> This second image removes the ablity to boot the legacy OLPC OS kernel,
> doesn't it?

For secure boot, yes.  But you could still use root=.

-- 
James Cameron
http://quozl.netrek.org/