Re: NetBSD9.0: 2020-02-28-netbsd9.0-raspi-earmv6hf.img

[Harold Gutch <logix%foobar.franken.de@localhost>]

Hi Ebihara-san,

On Fri, Feb 28, 2020 at 09:26:21AM +0900, Jun Ebihara wrote:
> 
> >> I've updated 2020-02-28-netbsd9.0-raspi-earmv6hf.img for RPI.
> >> http://cdn.netbsd.org/pub/NetBSD/misc/jun/raspberry-pi/NetBSD-9.0/2020-02-28-netbsd9.0-raspi-earmv6hf.img.gz
> >> RPI3A+: copy dtb from -current
> >>  copy /boot/bcm2837-rpi-3-a-plus.dtb 
> > Is this really needed?  A few weeks ago I tested booting the RPI2
> > kernel on an RPI 3 A+, and that worked even though I did not have a
> > bcm2837-rpi-3-a-plus.dtb .  I think the firmware with netbsd-9 loads
> > bcm2837-rpi-3-b.dtb (or perhaps 3-b-plus.dtb) instead.
> 
> Ah,I've updated newer firmware,which need bcm2837-rpi-3-a-plus.dtb.
> Back to the original on next 9.x version.

Ah, OK, that explains it of course.


> #I should delete firmware update line,when copy Makefile.NetBSD8 to NetBSD9
> https://github.com/ebijun/NetBSD/blob/master/RPI/RPIimage/Image/Makefile.NetBSD9
> thanx for points my mistake.
> 
> >> dmesg:
> >> RPI2-1.2: 
> >>  https://github.com/ebijun/NetBSD/blob/master/dmesg/earmv6hf/NetBSD9/RPI2-1.2
> > Okuyama-san said that he had to build a .dtb manually for his RPI2 v1.2,
> > but I don't know if that was for current or netbsd-9 - are you saying
> > that you did not have to do this?  I don't have an RPI2 v1.2 yet,
> > otherwise I would just test myself.
> 
> On this image (diffrent firmware from 9.0),RPI2-1.2 boot well without any tricks.

Oh, interesting - so the firmware in current falls back to one of the
.dtbs we have there, but the one in 9.0 does not and needs what
Okuyama-san described.

Thanks for the info, this is good to know.  Also thank you for putting
all that work in your image, nice work!


  Harold