Rasbperry Pi, what should TARGET_ARCH be?

[Glen Barber]

Hi,

I've been working on adding support for embedded systems to the release
scripts, which set up a chroot to ensure a clean build environment, then
runs Tim's Crochet scripts.

For the RPI-B, recent updates to the build scripts work fine for
11.0-CURRENT and 10.0-STABLE.  However, 10.0-RELEASE images fail to
boot.

I showed output from 'uname -pm' out-of-band of an 11.0-CURRENT image,
and was suspicious that the output showed 'arm arm', not 'arm armv6'.
Warner had the same impression it should be 'arm armv6'.

Hiren poked around the Crochet code, and saw that 'TARGET_ARCH=arm' is
set for the RaspberryPi board by default.

As a "just in case" experiment, I retried the 10.0-RELEASE code
(release/10.0.0/) with TARGET_ARCH=armv6, and sure enough, it works.

But, I don't know *why*.

Is this a change between head/ and stable/10/ versus releng/10.0/ ?

I can handle a differentiation between the branches with regard to this
(sort of), but I want to make sure the correct TARGET_ARCH is being set
across the different branches, so it can be handled properly in the
build scripts, and usable images can be produced.

So, what should be used?  And where?

Thanks for any input,

Glen

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 834 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20140124/8dcedc9d/attachment.sig>