Received: by 10.192.165.148 with SMTP id m20csp1332232imm; Wed, 2 May 2018 19:34:33 -0700 (PDT) X-Google-Smtp-Source: AB8JxZp5jsEUr2pAxmndimEopPNzIaPZv/2tur4ciIOkUBTpeUFMRfMmuxIsW1TlJpaHznlDqV1z X-Received: by 2002:a63:7d43:: with SMTP id m3-v6mr11302728pgn.117.1525314873478; Wed, 02 May 2018 19:34:33 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525314873; cv=none; d=google.com; s=arc-20160816; b=eSFl2lvgKdOUv+jhTLBATyRlthXD3zw0S7p5DNXmcVcFLKq3arKabLxGtS9/axPCqs qSBEwwdIngI8Ol5ADjvaDyPy5LCxyWR7X67fsG/f8mXf0Th5SFwHbEkliQqJLa2806BZ BY/V6MP2VwYBbTYIDpnSx5qpiQBV57ecQPU6dNAZdCtyZixMnDMvondF5kxp6T3kV+s/ obus2w0qz8G5cpDPH5uE/ulq3PdYRtGSMQ3lUiNv+P/qpAgPq3fCQFrhFWwUIK8jcwzc VYqC6gy9vlunjptlyrnmrgYBZ5S1O2Sm0754SE6csB57aB6EkqC0qbq82UsN9JRYw6EX i0CQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=y7Wv61YSPD3X7LvtyzyzrpvSf7VmtFC+Q0YEeJe/4ng=; b=XNiTMs9AWReRQCrlUiYvqNK9HPQY5XUr2yeGaZ2IosryK0pZtziz54ITAyxAco8C6Q E+0xtZRy8FL4XMDoNeDSceSlCE1QXzKisXG+BcQQ4Pk0lgr+21ViKGgeOor128ZQ3kme Is0JZzK2J6FhPAqDwwmJMEyGZniABzvaKwViif4VK+4cJvUN1RYKdAqEygaK++itwVed /G8rrFny1eJmPwUMPMnsV2LCpeqWoz+pjJTYT4bLCuWB3xAtlZtKj7X6oqmrJI4zvmV5 LfYchySs6t6A4A74aMQfpBDLnPrN3fJXdGVtlg5sFdhbMmuwZqDUes3JyVZ+VtvJ45EZ pw+w== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a61-v6si12706970pla.400.2018.05.02.19.34.19; Wed, 02 May 2018 19:34:33 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752130AbeECCdh (ORCPT + 99 others); Wed, 2 May 2018 22:33:37 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:53660 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752001AbeECCdf (ORCPT ); Wed, 2 May 2018 22:33:35 -0400 Received: from dalias by brightrain.aerifal.cx with local (Exim 3.15 #2) id 1fE43c-0006q7-00; Thu, 03 May 2018 02:33:20 +0000 Date: Wed, 2 May 2018 22:33:20 -0400 From: Rich Felker To: John Paul Adrian Glaubitz Cc: Rob Landley , Yoshinori Sato , linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [J-core] [PATCH v5 00/22] sh: LANDISK and R2Dplus convert to device tree Message-ID: <20180503023320.GD1392@brightrain.aerifal.cx> References: <1467564402-2649-1-git-send-email-ysato@users.sourceforge.jp> <8c75b447-fc14-871e-1a04-733132527b65@landley.net> <20171117191706.GF1627@brightrain.aerifal.cx> <7193aa1b-50e3-11d4-f93d-f567e2e06b8c@physik.fu-berlin.de> <20180105212857.GR1627@brightrain.aerifal.cx> <20180503013708.GC1392@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180503013708.GC1392@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 02, 2018 at 09:37:08PM -0400, Rich Felker wrote: > On Fri, Jan 05, 2018 at 04:28:57PM -0500, Rich Felker wrote: > > 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? > > Progress on all this! I've got my LANDISK working again, but with the > disk image Sato-san provided me, which is using (a patched?) U-Boot > and a kernel based on this patch series. I don't know how to recreate > the U-Boot setup from scratch, but I might be able to figure out how > to replace the kernel image it's using. It's possible I may be able to > get lilo working too -- I tried building it but I'm still not sure how > to use it, and in any case I need to image the existing system before > I clobber it since I'm not sure I have the original image. I found the U-Boot stuff here: https://ja.osdn.net/users/ysato/pf/uboot/wiki/FrontPage but I'm not sure how to install it yet. Will try to figure it out. Rich