Bug 222200 - aarch64 FreeBSD 11 image not available for RPI 3
Summary: aarch64 FreeBSD 11 image not available for RPI 3
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: arm (show other bugs)
Version: 11.1-RELEASE
Hardware: arm64 Any
: --- Affects Only Me
Assignee: FreeBSD Release Engineering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-10 16:57 UTC by Tarjei Jensen
Modified: 2019-01-07 23:01 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tarjei Jensen 2017-09-10 16:57:36 UTC
There seems to be a lack of 64bit aarch64 images for FreeBSD 11 in general. The images posted at 

https://download.freebsd.org/ftp/releases/arm64/aarch64/ISO-IMAGES/11.1/
https://download.freebsd.org/ftp/releases/arm64/aarch64/ISO-IMAGES/11.0/

seems to not be suitable for any of the popular aarch64 devices.

I notice that there is a lot of images for devices like the Raspberry PI 3 in the FreeBSD 12.0-CURRENT snapshot section.
https://download.freebsd.org/ftp/snapshots/arm64/aarch64/ISO-IMAGES/12.0/

The corresponding 11.0 section do not have images for these devices.

I find it weird that there is a lot of support in FreeBSD 12, but none for FreeBSD 11. And it is also annoying since I happen to need aarch64 FreeBSD 11 in order to test the gcc6-aux port which have an Ada compiler which does not work on FreeBSD 12.
Comment 1 Mark Millard 2017-09-10 20:28:31 UTC
(In reply to Tarjei Jensen from comment #0)

rpi3 support is and has been in development
as I understand.

Such development happens on head/ (CURRENT),
not on release/*/ , releng/*/ , or stable/*/ .

I do not know if rpi3 support in head involves
material that might not be reasonable to Move
From CURRENT (MFC) to stable/11/ . But rpi3
support would have to be judged ready for such
a move before it would happen.

After being in stable/11 (if ever) it would make
it into the next release/11.*/ --but not likely
before that. I do not know that such a sequence
is likely, much less in any short time frame.
It may wait for release/12.0/ for all I know.
Comment 2 Tarjei Jensen 2017-09-10 21:11:15 UTC
As pointed out : it is already in release 12.
Comment 3 Mark Millard 2017-09-10 21:22:14 UTC
(In reply to Tarjei Jensen from comment #2)

There is no release/12.0/ yet. Only head/ .
No releng/12.*/ and no stable/12/ yet.

See:

https://svnweb.freebsd.org/base/release/
https://svnweb.freebsd.org/base/releng/
https://svnweb.freebsd.org/base/stable/

compared to:

https://svnweb.freebsd.org/base/head/
Comment 4 Jonathan Chen 2017-09-10 21:29:09 UTC
Initial RPI3 development was done on FreeBSD 11, as can be seen at:
https://wiki.freebsd.org/arm64/rpi3

Unfortunately, somewhere along the way support for RPI3 on FreeBSD 11 got lost. It would be nice if some TLC could be given to (at the very least) a buildable RPI3 boot image on 11-STABLE.
Comment 5 Mark Millard 2017-09-10 23:44:37 UTC
(In reply to Jonathan Chen from comment #4)

As I understand it when release/11.0/ and head split
rpi3 support was still considered insufficient for
development in stable/11/ or releng/11.*/ or
release/11.*/ . So it stayed in head.

In fact https://svnweb.freebsd.org/base/head/release/arm64/RPI3.conf?view=log

shows its first version as under 3 months ago:

Revision 320252 - (view) (download) (annotate) - [select for diffs] 
Added Fri Jun 23 00:08:36 2017 UTC (2 months, 2 weeks ago) by gjb 
File length: 2137 byte(s)

This is long after release/11.0/ . Prior to that
head did not have an rpi3 snapshots either as I
understand.
Comment 6 Glen Barber freebsd_committer 2017-09-12 15:29:37 UTC
Last I manually built a RPI3 image against stable/11, it failed to boot properly.  It would get far enough into loader where it would panic, and instantly reboot.  I have not had time to diagnose this further, but only see the problem on 11.x.
Comment 7 Glen Barber freebsd_committer 2017-09-13 16:56:52 UTC
I have confirmed that the 11-STABLE RPI-3 images continue to insta-panic, so it does not make sense to produce these images just yet.
Comment 8 Tarjei Jensen 2017-09-13 17:07:04 UTC
(In reply to Glen Barber from comment #7)

Is there any contact with the people who created the v 12.0-CURRENT boot image?