From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752218AbeEOBmI (ORCPT ); Mon, 14 May 2018 21:42:08 -0400 Received: from 216-12-86-13.cv.mvl.ntelos.net ([216.12.86.13]:54136 "EHLO brightrain.aerifal.cx" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752024AbeEOBmH (ORCPT ); Mon, 14 May 2018 21:42:07 -0400 Date: Mon, 14 May 2018 21:41:52 -0400 From: Rich Felker To: Yoshinori Sato Cc: John Paul Adrian Glaubitz , Rob Landley , 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: <20180515014152.GV1392@brightrain.aerifal.cx> References: <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> <20180503023320.GD1392@brightrain.aerifal.cx> <048ab147-21b8-045d-d21c-e1be2dd0e954@physik.fu-berlin.de> <87k1sgtf8t.wl-ysato@users.sourceforge.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87k1sgtf8t.wl-ysato@users.sourceforge.jp> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 07, 2018 at 10:40:34AM +0900, Yoshinori Sato wrote: > On Thu, 03 May 2018 19:07:38 +0900, > John Paul Adrian Glaubitz wrote: > > > > [1 ] > > Hi Rich! > > > > On 05/03/2018 04:33 AM, Rich Felker wrote: > > > 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. > > > > Interesting. It seems the HDL-160U uses u-boot instead of lilo which > > is used on my USL-5P. Both are based on the LANDISK platform though. > > I wonder whether it is possible to convert the USL-5P to use u-boot > > instead of the very limited lilo. > > > > As for the kernel configuration, for USL-5P, I had to use the kernel > > configuration attached to this mail. One important configuration setting > > is CONFIG_SH_PCLK_FREQ which has to be set to "33250000" otherwise > > the kernel won't boot properly. > > > > I still have my USL-5P ready to be set up for testing a new kernel > > image with the device tree patches merged. Although I still don't > > know how to enable the internal (pseudo) IDE controller. > > > > @Yoshinori: > > > > Did the HDL-160U LANDISK device you have use u-boot by default or > > did you convert it from lilo? > > Yes. > Replace sh-lilo's second stage with u-boot. > With this method it is unnecessary to rewrite Flash for boot. Can you give me a brief explanation of how to reproduce the bootloader installation? For now I'm just using the existing MBR/partitioning you sent me, and replacing zImage.itb in /boot makes it attempt to load a new kernel, but I haven't gotten any output yet to know if it's working. Probably the most important thing I'm missing right now is what the its file for generating the zImage.itb should look like. I tried making one myself but it may be wrong. I'm also unsure whether I should use a zImage or vmlinux file as input, and if using a zImage file, what load address I should choose. For now I'm using the upstream landisk board support (maybe not working, we'll see). Once I can confirm I'm getting some output and the kernel seems minimally functional, I'm going to switch to DT, but integrating the DT stuff with u-boot isn't important right away since I can start with a linked-in DT. At some point I'd also like to know how to reinstall u-boot on the MBR or whatever. Rich