Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Jun 2017 08:40:48 -0700
From:      Mark Millard <markmi@dsl-only.net>
To:        Emmanuel Vadot <manu@bidouilliste.com>
Cc:        Warner Losh <imp@bsdimp.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: Next up on creating armv7 MACHINE_ARCH: pre FCP stage
Message-ID:  <FC393FFD-7461-40C6-9282-076016A2C567@dsl-only.net>
In-Reply-To: <20170615145107.97e6460fbb6222b258bfd614@bidouilliste.com>
References:  <CANCZdfqw4dwkrMtNO9zpdnuXkrmVrWf_M4Odcn5MY%2B0jz7h_dA@mail.gmail.com> <C0FEFDC3-A873-4110-928A-E534D3FB5FE7@dsl-only.net> <6EC26472-CE31-4B14-A049-3F153E590647@dsl-only.net> <20170615145107.97e6460fbb6222b258bfd614@bidouilliste.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2017-Jun-15, at 5:51 AM, Emmanuel Vadot <manu@bidouilliste.com> =
wrote:

> On Thu, 15 Jun 2017 02:08:10 -0700
> Mark Millard <markmi@dsl-only.net> wrote:
>=20
>> On 2017-Jun-14, at 11:20 PM, Mark Millard <markmi at dsl-only.net> =
wrote:
>>=20
>>> On 2017-Jun-14, at 10:22 PM, Warner Losh <imp at bsdimp.com> wrote:
>>>=20
>>>> . . .
>>>> Comments?
>>>=20
>>> I booted Ubuntu Mate on a BPI-M3 and tried:
>>>=20
>>> $ uname -p
>>> armv7l
>>>=20
>>> $ uname -ap
>>> Linux bpi-iot-ros-ai 3.4.39-BPI-M3-Kernel #1 SMP PREEMPT Tue May 3 =
13:47:01 UTC 2016 armv7l armv7l armv7l GNU/Linux
>>>=20
>>> I was actually thinking that a "hf" might
>>> show up in how they name things if it was
>>> a hard float based build. But looking I
>>> see in /lib/ :
>>>=20
>>> . . .
>>> drwxr-xr-x  3 root root  16384 Nov  4  2016 arm-linux-gnueabihf
>>> . . .
>>> lrwxrwxrwx  1 root root     30 Oct 14  2016 ld-linux-armhf.so.3 -> =
arm-linux-gnueabihf/ld-2.23.so
>>> lrwxrwxrwx  1 root root     24 Apr 21  2016 ld-linux.so.3 -> =
/lib/ld-linux-armhf.so.3
>>> . . .
>>>=20
>>> and in /lib/arm-linux-gnueabihf/ :
>>>=20
>>> lrwxrwxrwx 1 root root 10 Oct 14  2016 =
/lib/arm-linux-gnueabihf/ld-linux-armhf.so.3 -> ld-2.23.so
>>>=20
>>> so it appears armv7l was used for naming a
>>> hard float build in uname -p.
>>>=20
>>> Of course this does not check how uniform the
>>> various linux distributions are about such
>>> naming.
>>>=20
>>> Still it may mean that for linux-matching "armv7"
>>> might not be the right name for uname -p output.
>>=20
>> I tried another linux on the BPI-M3: gentoo .
>>=20
>> # uname -p
>> ARMv7 Processor rev 5 (v7l)
>>=20
>> (Wow. Not what I expected.)
>>=20
>> # uname -pa
>> Linux bananapi 3.4.39-BPI-M3-Kernel #1 SMP PREEMPT Tue May 3 13:47:01 =
UTC 2016 armv7l ARMv7 Processor rev 5 (v7l) sun8i GNU/Linux
>>=20
>> # uname -m
>> armv7l
>>=20
>> # uname -i
>> sun8i
>>=20
>> # ls -l /lib/ld-*
>> -rwxr-xr-x 1 root root 134192 Mar 26  2016 /lib/ld-2.21.so
>> lrwxrwxrwx 1 root root     10 Mar 26  2016 /lib/ld-linux-armhf.so.3 =
-> ld-2.21.so
>>=20
>> So again armv7l seems to be the base name used for
>> a hardfloat little-endian context --although it
>> appears that "uname -m" gives text more likely to
>> be used in testing for how to configure to match
>> the live context. "uname -p" seems far less
>> standardized for its results. The same for
>> "uname -i".
>>=20
>> =3D=3D=3D
>> Mark Millard
>> markmi at dsl-only.net
>=20
> On both your linux you are using linux-sunxi which is a fork of the
> Allwinner kernel "maintained" by the sunxi community (and it is old).
> To have the proper values of uname one should test running linux
> vanilla kernel.

They both reported (extracted from the earlier text
that I sent):

3.4.39-BPI-M3-Kernel
3.4.39-BPI-M3-Kernel

It is the same kernel version from the same group
for the same hardware context as far as what each
reported.

While they may have varied the kernel for some
reason without changing the version identification
that is not want I would expect.

I expected it was the Ubuntu vs. Gentoo code that
makes the difference, not the kernel.

I'm not aware of a modern vanilla kernel for the
BPI-M3.

=46rom what I can tell for little armv7 boards like
this having older kernels is a common case and
is something ports code would normally deal with
upstream. It is not just sunxi as I understand.

I may do more experiments and report those too.
My notes are just information for Warner and others
to consider.

=3D=3D=3D
Mark Millard
markmi at dsl-only.net




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FC393FFD-7461-40C6-9282-076016A2C567>