[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netbsd-port-arm
Subject:    Re: sysupgrade didn't update kernel on Pi-2
From:       Hal Murray <hmurray () megapathdsl ! net>
Date:       2019-06-25 10:57:19
Message-ID: 20190625105719.B12DB40605C () ip-64-139-1-69 ! sjc ! megapath ! net
[Download RAW message or body]


logix@foobar.franken.de said:
>> Is a PR appropriate?  Should susupgrade update /boot/ on ARM systems?

> Good question - your situation was unfortunate, but I'm not sure if
> sysupgrade should touch /boot.  One argument against this is that the boot
> process on the various ARM boards differs quite a lot, and this would mean
> making sysupgrade aware of every single one, including possibly installing
> updated versions of u-boot.

> Personally, I don't think there should be much more than perhaps an
> additional paragraph in the manpage and/or some informational output by
> sysupgrade if run on a platform where this is an issue (like evbarm).

I'd be happy if sysupgrade didn't touch u-boot.

If so, all that's left to upgrade in /boot/ is the kernel.  The text that 
would be added to the man page doesn't seem like it would be much less 
complicated than the code to actually do the upgrade.

That's assuming the tag such as "RPI2" is readily available to sysupgrade.  I 
don't see an easy way to get it, but I don't know my way around that stuff.

-- 
These are my opinions.  I hate spam.




[prev in list] [next in list] [prev in thread] [next in thread]