Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree

[Rich Felker]

On Fri, Nov 17, 2017 at 08:54:47PM +0100, John Paul Adrian Glaubitz wrote:
> On 11/17/2017 08:17 PM, Rich Felker wrote:
> > There were significant problems that I don't think were ever
> > addressed, including incompatible changes in how boot command line was
> > handled and possibly ambiguity about what a physical address means
> > (zero based vs based in the zone SH3/4 excludes from MMU mapping) in
> > the contract for how the bootloader passes a DTB pointer in to the
> > kernel, or something similar.
> 
> I see, thanks for the heads-up.
> 
> > This is a large part of why I want to get to the point where I can
> > build and boot a kernel on the LANDISK -- not being able to test any
> > of this is a blocker for moving everything to device tree.
> 
> I can actually help you with that. I know what to do to get the kernel
> to boot on the LANDISK device. I've got everything working except
> being unable to detect the IDE controller. The attached config builds
> a kernel which boots with the attached output.
> 
> Furthermore, in order to install the kernel, you need to use the
> cross-LILO version from [1] which allows to install the bootloader
> on an x86 machine into the SuperH LANDISK image.
> 
> Instructions can be found in [2]. A base filesystem can be found in [3].
> 
> And I could also send you an USL-5P which is also a LANDISK device,
> just in a different form-factor.
> 
> Adrian
> 
> > [1]http://iohack.osdn.jp/kogiidena/debian26/base/landisk-tools-20070612.tgz
> > [2] https://www.with.de/fw/pub/Computing/PlextorPX-EH/LANDISKdebian.pdf
> > [3] http://iohack.osdn.jp/kogiidena/debian26/base/

I'm trying to reproduce this but can't find any documentation for
cross-LILO in [2], much less any code except possibly the binary
"lilo.x86" in [1]. Googling cross-lilo isn't finding anything
meaningful except this thread. Is there anywhere to find source and
information on what it's doing, or is this going to be something I
have to reverse-engineer?

Rich