Re: why is armv7 GENERICSD in 13.0-RELEASE?

Emmanuel Vadot <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Thu, 15 Apr 2021 18:22:27 +0100
tech-lists <[email protected]> wrote:

> (not sure where else to post this, -arm seemed most appropiate at first
> glance)
> 
> As per subject. I went looking for armv7-rpi2b images. I could find
> aarch64-rpi images and arm-armv6-rpb images but for some reason the
> armv7-rpi2b image is called armv7-GENERICSD[1]. The only way of working
> out if it could be suitable for rpi2b was to download, unpack the image
> and mount the msdos partition with mdconfig to see that among the files
> there, there's bcm2709-rpi-2-b.dtb. There's lots of armv7 hardware out
> there not rpi2b. There is only one armv6 image and that is labelled as
> rpi-b. There is only one armv7 image and that's labelled as GENERICSD
> ?!? 
> 
> 1. why can't a naming convention be decided on and adhered to

 I want to add a GENERICSD image for aarch64 for a long time, it wasn't
possible before because some boards where using GPT while most of the
others where using MBR. Now that Allwinner can be used with GPT a
GENERICSD can be made (and only RPI will be left with MBR, even if I
think that some of the RPI4 can boot from GPT)

> 2. when naming convention changes, please make some sort of announcement
> on the main freebsd website.

 The commit was taggued with Relnotes, not sure why it wasn't added to
them.
https://cgit.freebsd.org/src/commit/?id=e6b9cee76b14d687fb7ee6e37f381349b749401b

> [1] https://download.freebsd.org/ftp/releases/ISO-IMAGES/13.0/FreeBSD-13.0-RELEASE-arm-armv7-GENERICSD.img.xz
> 
> thanks,
> -- 
> J.


-- 
Emmanuel Vadot <[email protected]> <[email protected]>
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.