From nobody Mon Nov 25 15:31:51 2024 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4XxqTC0jxxz5dmWv for ; Mon, 25 Nov 2024 15:32:31 +0000 (UTC) (envelope-from marietto2008@gmail.com) Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XxqTB657yz44dn for ; Mon, 25 Nov 2024 15:32:30 +0000 (UTC) (envelope-from marietto2008@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x42f.google.com with SMTP id d2e1a72fcca58-7250c199602so1048286b3a.1 for ; Mon, 25 Nov 2024 07:32:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1732548749; x=1733153549; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vuk4L4yOjFUy+6KI8bLYigHopm4heQ36ntyyx3Qq4Fk=; b=mv7erowmkG5FjeiqxAgpe1707lEj/Qk+yEeC0dHTE3T4qitls4UACgaISizdC3zPRZ 29ZYdic/1BlBGFqDWqLHAYI2aqBp2N0zH2RHEfpeZKiVnDp5D0upYBMZv2vE5jnIygnC 3bKKXN//5si7DNKw0xF1fbJKFJSWsefYzFqyCLvCfeem0pqY2cV46LkN8VFp/qnTjpGa LuRvd2eMtill7uvIB4NBhiD8xQ4QYFYDKPBxak9wL7BVVGkZx1GE5l8y/i4FpTsxLlCT mD6Cpz/F5VUav5F/cVuIg+Vpblo4Aj4OhkBKb+lpDhNLr7IU2pNjM2lKMuwAZqqgERBC t8yA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1732548749; x=1733153549; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vuk4L4yOjFUy+6KI8bLYigHopm4heQ36ntyyx3Qq4Fk=; b=wWwVP9vWUUzTN0IZTu/AgAG8Ilk9RFRSqmxrq1ztPyBUspT+5pjH/19OlXl+vKp8qS UZzK6afVGOSSa0HKuBNECEJk/Z7Ilb0RwFD9eQjU5LC9Isz6tXGrMjgvH8VQqQ1GcPjr m1AWJJ+1Y3H4+V+oVNCsKMZbU7yUKmmO0nFpozBdUmDxA5QyJprY6marUpwNY+3BtofC FJuECREmVKiR7CTgcqkCf1z6NmzaPuYlg9T+v53wwOqy5GKD3QXpEKS2qo5uhF2GcoUI htOiF0W7pNesJuKyIUQ5HeuK8D92JMPoD7rId+SFXrIXMfsP6DnM15PAyjbWv+c7FM+Q lWpQ== X-Forwarded-Encrypted: i=1; AJvYcCWSfjbbDj6VBfO9N9Yrr0rmXcR37RW/SP0mN2XUL5vRpNKQqmCtEUuTlWGZ01rTC190p3gM+SZjpsoqQg==@freebsd.org X-Gm-Message-State: AOJu0Yw8keCBgzmb4NApS+MDfVrnlUTC1EiHKhEh7tHGDP5I7u3jRpVs tck4ptn7lGwf1uiX16Qw7wHCVV+XjfzqueViDqsXcGNyVvBHseuB6jyBEAxRF/Csz6Dl59jiD1S esUVLcfxh3us3pvkKcDWElUvQDv4= X-Gm-Gg: ASbGncvsbsiC3R+de3CUyiM/QyCNtGpok7xC4+O2LKnE5t1c7FMYDQI9BuBnZOLZ1GK UgAhrly0WMXf0+X9f4ktJ9TXRy+UB6N4= X-Google-Smtp-Source: AGHT+IHWnCJcrHDj1HBeVbHu9A+xtnuogdFwt1KcvHzldzFLuT2iRurfRwDvVvSE+u/09bDLvLNEG6zwqbPC72VKioA= X-Received: by 2002:a17:902:e843:b0:20c:ef90:e4b5 with SMTP id d9443c01a7336-2129f75a772mr206724905ad.52.1732548747865; Mon, 25 Nov 2024 07:32:27 -0800 (PST) List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@FreeBSD.org MIME-Version: 1.0 References: <9211C7C9-FB09-4EB0-A315-BB86865EE9BC@yahoo.com> In-Reply-To: From: Mario Marietto Date: Mon, 25 Nov 2024 16:31:51 +0100 Message-ID: Subject: Re: Radxa Zero and FreeBSD : happy marriage ? To: Warner Losh Cc: Ganbold Tsagaankhuu , Mark Millard , freebsd-arm Content-Type: multipart/alternative; boundary="000000000000ac388b0627be7092" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XxqTB657yz44dn X-Spamd-Bar: ---- --000000000000ac388b0627be7092 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ok. So the radxa is a soc that can't be used. At the moment I'm not sure what soc is good for this project. The only soc that seems to be usable is the raspberry pi zero 2W. But it has only 500MB of memory so it can run X and only a few apps. Not a good SOC for creating a mobile phone. For sure there are a lot of socs in the market,but they aren't slim. You know,a mobile phone should have a maximum of 1.5 cm of thickness or it does not resemble a mobile device and it is not appetible for the eyes. I'm working on this project with another person. We have to choose carefully the hardware components because FreeBSD has some limitations. There aren't drivers for the display (they are developed for Linux,mostly) and the problem of the - power consumption. FBSD's kernel itself consumes more than Linux kernel even after tuning. It is because the FBSD team did not ever consider running embedded battery powered devices. They cared about not overheating the CPU, but not to save power. One of the keys (besides the kernel codebase) - is knowing from documentation how to manage internal SoC's clocks and peripherals (turn them on and off, tuning clocks frequency, etc.). So, that is why we insisted that the SoC has to be properly documented to withstand the goals of the project. Otherwise, we will run out of even powerful batteries within a couple hours. The most hungry consumer is the screen. So it is mandatory to have an ability to turn it off completely, but still run the kernel in power-save mode. So,we think that we can use,at least to start, the raspberry pi zero 2W that has the advantage of being very widely known and supported by the community. It can run kernel + X + some apps. We target 512Mb boards as well at the time until it is not tough to fit everything we need. Due to the lack of drivers for the display,we are forced to use USB/HDMI screens that are driver-less. We know that we can buy them from Elecrow,for example. This could be the only solution. The model that we are looking for should not use a driver board and no drivers. Maybe one HDMI display is overkill for our phone. But for sure it should be powered by attaching it to the USB port of the SOC. Size should be between 4 and 5 inches. On Mon, Nov 25, 2024 at 4:12=E2=80=AFPM Warner Losh wrote: > I was gifted a Radxa many years ago... And it looked like a lot of work > to bring things up on it, not least because the boot loader was weird to > even get started with uboot, and the uboot you needed was a fork of an > ancient branch of upstream uboot. Tha AmLogic datasheets at the time were > unobtanium, but have since become findable (I'm told by someone I chatted > about the Radxa at I think BSDcan over beers before covid). I gave up due > to the large amount of work it would have been to translate everything fr= om > just the Linux sources. > > Warner > > On Mon, Nov 25, 2024 at 8:03=E2=80=AFAM Ganbold Tsagaankhuu > wrote: > >> Amlogic is not supported in FreeBSD at all and nobody is working on this >> SoC, so if I were you I wouldn't buy it. >> >> On Mon, Nov 25, 2024, 10:49=E2=80=AFPM Mario Marietto >> wrote: >> >>> Thanks. I see more development with this model : >>> >>> http://radxa.com/products/zeros/zero3e/#techspec >>> >>> according to this thread : >>> >>> https://forum.radxa.com/t/zero-3e-freebsd/20661 >>> >>> Unfortunately this soc is not slender as the previous one. And anyway,a >>> lot of functions don't work on FreeBSD. >>> >>> >>> On Mon, Nov 25, 2024 at 3:32=E2=80=AFPM Mark Millard wrote: >>> >>>> On Nov 25, 2024, at 03:02, Mario Marietto >>>> wrote: >>>> >>>> > I'm planning to buy this soc : >>>> > Radxa Zero >>>> > =E2=80=A2 Specifications: >>>> > =E2=80=A2 CPU: Amlogic S905Y2 quad-core Cortex-A53 >>>> > =E2=80=A2 RAM: Up to 4GB LPDDR4 (4GB option available) >>>> > =E2=80=A2 Ports: >>>> > =E2=80=A2 Mini HDMI >>>> > =E2=80=A2 Micro USB OTG >>>> > =E2=80=A2 Micro USB power >>>> > =E2=80=A2 Wireless: Wi-Fi 802.11 b/g/n/ac, Bluetooth 5.0 >>>> > >>>> > because I'm trying to assemble a mobile phone powered by FreeBSD. >>>> This soc seems to be the only option available given its performances = and >>>> slenderness. >>>> > But what I want to know is how compatible it is with FreeBSD. Are >>>> there some huge unfixed bugs ? Problems with HDMI or whatever ? thanks= . >>>> >>>> It does not appear to have a FreeBSD U-Boot port, making it >>>> seem unlikely that the kernel work has been done to support >>>> the soc. >>>> >>>> For reference: >>>> >>>> # ls -dC1 /usr/ports/sysutils/u-boot-*/ >>>> /usr/ports/sysutils/u-boot-a13-olinuxino/ >>>> /usr/ports/sysutils/u-boot-a64-olinuxino/ >>>> /usr/ports/sysutils/u-boot-bananapi/ >>>> /usr/ports/sysutils/u-boot-bananapim2/ >>>> /usr/ports/sysutils/u-boot-beaglebone/ >>>> /usr/ports/sysutils/u-boot-bhyve-arm64/ >>>> /usr/ports/sysutils/u-boot-bhyve-riscv/ >>>> /usr/ports/sysutils/u-boot-chip/ >>>> /usr/ports/sysutils/u-boot-clearfog/ >>>> /usr/ports/sysutils/u-boot-cubieboard/ >>>> /usr/ports/sysutils/u-boot-cubieboard2/ >>>> /usr/ports/sysutils/u-boot-cubox-hummingboard/ >>>> /usr/ports/sysutils/u-boot-firefly-rk3399/ >>>> /usr/ports/sysutils/u-boot-imx-serial-loader/ >>>> /usr/ports/sysutils/u-boot-master/ >>>> /usr/ports/sysutils/u-boot-nanopi-a64/ >>>> /usr/ports/sysutils/u-boot-nanopi-m1plus/ >>>> /usr/ports/sysutils/u-boot-nanopi-neo-air/ >>>> /usr/ports/sysutils/u-boot-nanopi-neo/ >>>> /usr/ports/sysutils/u-boot-nanopi-neo2/ >>>> /usr/ports/sysutils/u-boot-nanopi-r2s/ >>>> /usr/ports/sysutils/u-boot-nanopi-r4s/ >>>> /usr/ports/sysutils/u-boot-nanopi-r5s/ >>>> /usr/ports/sysutils/u-boot-olimex-a20-som-evb/ >>>> /usr/ports/sysutils/u-boot-olinuxino-lime/ >>>> /usr/ports/sysutils/u-boot-olinuxino-lime2-emmc/ >>>> /usr/ports/sysutils/u-boot-olinuxino-lime2/ >>>> /usr/ports/sysutils/u-boot-orangepi-one/ >>>> /usr/ports/sysutils/u-boot-orangepi-pc-plus/ >>>> /usr/ports/sysutils/u-boot-orangepi-pc/ >>>> /usr/ports/sysutils/u-boot-orangepi-pc2/ >>>> /usr/ports/sysutils/u-boot-orangepi-plus-2e/ >>>> /usr/ports/sysutils/u-boot-orangepi-r1/ >>>> /usr/ports/sysutils/u-boot-orangepi-zero-plus/ >>>> /usr/ports/sysutils/u-boot-orangepi-zero/ >>>> /usr/ports/sysutils/u-boot-pandaboard/ >>>> /usr/ports/sysutils/u-boot-pcduino3/ >>>> /usr/ports/sysutils/u-boot-pine-h64/ >>>> /usr/ports/sysutils/u-boot-pine64-lts/ >>>> /usr/ports/sysutils/u-boot-pine64/ >>>> /usr/ports/sysutils/u-boot-pinebook/ >>>> /usr/ports/sysutils/u-boot-pinebookpro/ >>>> /usr/ports/sysutils/u-boot-qemu-arm/ >>>> /usr/ports/sysutils/u-boot-qemu-arm64/ >>>> /usr/ports/sysutils/u-boot-qemu-riscv64/ >>>> /usr/ports/sysutils/u-boot-quartz64-a/ >>>> /usr/ports/sysutils/u-boot-quartz64-b/ >>>> /usr/ports/sysutils/u-boot-riotboard/ >>>> /usr/ports/sysutils/u-boot-rock-pi-4/ >>>> /usr/ports/sysutils/u-boot-rock64/ >>>> /usr/ports/sysutils/u-boot-rockpro64/ >>>> /usr/ports/sysutils/u-boot-rpi-0-w/ >>>> /usr/ports/sysutils/u-boot-rpi-arm64/ >>>> /usr/ports/sysutils/u-boot-rpi/ >>>> /usr/ports/sysutils/u-boot-rpi2/ >>>> /usr/ports/sysutils/u-boot-rpi3-32/ >>>> /usr/ports/sysutils/u-boot-rpi3/ >>>> /usr/ports/sysutils/u-boot-rpi4/ >>>> /usr/ports/sysutils/u-boot-sifive-fu540/ >>>> /usr/ports/sysutils/u-boot-sifive-fu740/ >>>> /usr/ports/sysutils/u-boot-sinovoip-bpi-m3/ >>>> /usr/ports/sysutils/u-boot-sopine-spi/ >>>> /usr/ports/sysutils/u-boot-sopine/ >>>> /usr/ports/sysutils/u-boot-starfive-visionfive2/ >>>> /usr/ports/sysutils/u-boot-tools/ >>>> /usr/ports/sysutils/u-boot-wandboard/ >>>> >>>> >>>> =3D=3D=3D >>>> Mark Millard >>>> marklmi at yahoo.com >>>> >>>> >>> >>> -- >>> Mario. >>> >> --=20 Mario. --000000000000ac388b0627be7092 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ok. So the radxa is a soc that can't be used. At = the moment I'm not sure what soc is good for this project. The only soc= that seems to be usable is the raspberry pi zero 2W. But it has only 500MB= of memory so it can run X and only a few apps. Not a good SOC for creating= a mobile phone. For sure there are a lot of socs in the market,but they ar= en't slim. You know,a mobile phone should have a maximum of 1.5 cm of t= hickness or it does not resemble a mobile device and it is not appetible fo= r the eyes.

I'm working on this pro= ject with another person. We have to choose carefully=20 the hardware components because FreeBSD has some limitations. There=20 aren't drivers for the display (they are developed for Linux,mostly) an= d the problem of the - power consumption. FBSD's kernel=20 itself consumes more than Linux kernel even after tuning. It is because=20 the FBSD team did not ever consider running embedded battery powered=20 devices. They cared about not overheating the CPU, but not to save=20 power. One of the keys (besides=20 the=20 kernel codebase) - is knowing from documentation how to manage internal=20 SoC's clocks and peripherals (turn them on and off, tuning clocks=20 frequency, etc.). So, that is why we insisted that the SoC has to be=20 properly documented to withstand the goals of the project. Otherwise,=20 we will run out of even powerful batteries within a couple hours. The most = hungry consumer is the screen. So it is mandatory to=20 have=20 an ability to turn it off completely, but still run the kernel in=20 power-save mode.

So,we think that we can use,at least to start, the raspberry pi zero 2W that has the advantage of=20 being very widely known and supported by the community. It can run=20 kernel + X + some apps. We target 512Mb boards as well at the time until it is not tough to fit=20 everything we need.

Due to the lack of=20 drivers for the display,we are forced to use USB/HDMI screens that are=20 driver-less. We know that we can buy them from Elecrow,for example. This co= uld be=20 the only solution. The model that we are looking for should not use a drive= r board and no drivers. Maybe one HDMI display is overkill for our phone. But for=20 sure it should be powered by attaching it to the USB port of the SOC.=20 Size should be between 4 and 5 inches.

On Mon, Nov 25, 2024 at 4= :12=E2=80=AFPM Warner Losh <imp@bsdimp.com> wrote:
I was gifted=C2=A0a Radxa many years= ago...=C2=A0 And it looked like a lot of work to bring things up on it, no= t least because the boot loader was weird to even get started with uboot, a= nd the uboot you needed was a fork of an ancient branch of upstream uboot. = Tha AmLogic datasheets at the time were unobtanium, but have since become f= indable (I'm told by someone I chatted about the Radxa=C2=A0at I think = BSDcan over beers before covid). I gave up due to the large=C2=A0amount of = work it would have been to translate everything from just the Linux sources= .

Warner

On Mon, Nov 25, 2024 at 8:03=E2=80=AFAM Ga= nbold Tsagaankhuu <ganbold@gmail.com> wrote:

Amlogic is not supported in FreeBSD at al= l and nobody is working on this SoC, so if I were you I wouldn't buy it= .


On Mon= , Nov 25, 2024, 10:49=E2=80=AFPM Mario Marietto <marietto2008@gmail.com> wrote:<= br>
Thanks. I see more development with this model :
=


according to this threa= d :


Unfortunately this soc= is not slender as the previous one. And anyway,a lot of functions don'= t work on FreeBSD.


On Mon, Nov 25, 2024 at 3= :32=E2=80=AFPM Mark Millard <marklmi@yahoo.com> wrote:
On Nov 25, 2024, at 03:02, = Mario Marietto <marietto2008@gmail.com> wrote:

> I'm planning to buy this soc :
> Radxa Zero
>=C2=A0 =C2=A0 =C2=A0=E2=80=A2 Specifications:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 CPU: Amlogic S905Y2 quad-co= re Cortex-A53
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 RAM: Up to 4GB LPDDR4 (4GB = option available)
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Ports:
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Mini HDMI
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Micro USB OTG=
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Micro USB pow= er
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=E2=80=A2 Wireless: Wi-Fi 802.11 b/g/= n/ac, Bluetooth 5.0
>
> because I'm trying to assemble a mobile phone powered by FreeBSD. = This soc seems to be the only option available given its performances and s= lenderness.
> But what I want to know is how compatible it is with FreeBSD. Are ther= e some huge unfixed bugs ? Problems with HDMI or whatever ? thanks.

It does not appear to have a FreeBSD U-Boot port, making it
seem unlikely that the kernel work has been done to support
the soc.

For reference:

# ls -dC1 /usr/ports/sysutils/u-boot-*/
/usr/ports/sysutils/u-boot-a13-olinuxino/
/usr/ports/sysutils/u-boot-a64-olinuxino/
/usr/ports/sysutils/u-boot-bananapi/
/usr/ports/sysutils/u-boot-bananapim2/
/usr/ports/sysutils/u-boot-beaglebone/
/usr/ports/sysutils/u-boot-bhyve-arm64/
/usr/ports/sysutils/u-boot-bhyve-riscv/
/usr/ports/sysutils/u-boot-chip/
/usr/ports/sysutils/u-boot-clearfog/
/usr/ports/sysutils/u-boot-cubieboard/
/usr/ports/sysutils/u-boot-cubieboard2/
/usr/ports/sysutils/u-boot-cubox-hummingboard/
/usr/ports/sysutils/u-boot-firefly-rk3399/
/usr/ports/sysutils/u-boot-imx-serial-loader/
/usr/ports/sysutils/u-boot-master/
/usr/ports/sysutils/u-boot-nanopi-a64/
/usr/ports/sysutils/u-boot-nanopi-m1plus/
/usr/ports/sysutils/u-boot-nanopi-neo-air/
/usr/ports/sysutils/u-boot-nanopi-neo/
/usr/ports/sysutils/u-boot-nanopi-neo2/
/usr/ports/sysutils/u-boot-nanopi-r2s/
/usr/ports/sysutils/u-boot-nanopi-r4s/
/usr/ports/sysutils/u-boot-nanopi-r5s/
/usr/ports/sysutils/u-boot-olimex-a20-som-evb/
/usr/ports/sysutils/u-boot-olinuxino-lime/
/usr/ports/sysutils/u-boot-olinuxino-lime2-emmc/
/usr/ports/sysutils/u-boot-olinuxino-lime2/
/usr/ports/sysutils/u-boot-orangepi-one/
/usr/ports/sysutils/u-boot-orangepi-pc-plus/
/usr/ports/sysutils/u-boot-orangepi-pc/
/usr/ports/sysutils/u-boot-orangepi-pc2/
/usr/ports/sysutils/u-boot-orangepi-plus-2e/
/usr/ports/sysutils/u-boot-orangepi-r1/
/usr/ports/sysutils/u-boot-orangepi-zero-plus/
/usr/ports/sysutils/u-boot-orangepi-zero/
/usr/ports/sysutils/u-boot-pandaboard/
/usr/ports/sysutils/u-boot-pcduino3/
/usr/ports/sysutils/u-boot-pine-h64/
/usr/ports/sysutils/u-boot-pine64-lts/
/usr/ports/sysutils/u-boot-pine64/
/usr/ports/sysutils/u-boot-pinebook/
/usr/ports/sysutils/u-boot-pinebookpro/
/usr/ports/sysutils/u-boot-qemu-arm/
/usr/ports/sysutils/u-boot-qemu-arm64/
/usr/ports/sysutils/u-boot-qemu-riscv64/
/usr/ports/sysutils/u-boot-quartz64-a/
/usr/ports/sysutils/u-boot-quartz64-b/
/usr/ports/sysutils/u-boot-riotboard/
/usr/ports/sysutils/u-boot-rock-pi-4/
/usr/ports/sysutils/u-boot-rock64/
/usr/ports/sysutils/u-boot-rockpro64/
/usr/ports/sysutils/u-boot-rpi-0-w/
/usr/ports/sysutils/u-boot-rpi-arm64/
/usr/ports/sysutils/u-boot-rpi/
/usr/ports/sysutils/u-boot-rpi2/
/usr/ports/sysutils/u-boot-rpi3-32/
/usr/ports/sysutils/u-boot-rpi3/
/usr/ports/sysutils/u-boot-rpi4/
/usr/ports/sysutils/u-boot-sifive-fu540/
/usr/ports/sysutils/u-boot-sifive-fu740/
/usr/ports/sysutils/u-boot-sinovoip-bpi-m3/
/usr/ports/sysutils/u-boot-sopine-spi/
/usr/ports/sysutils/u-boot-sopine/
/usr/ports/sysutils/u-boot-starfive-visionfive2/
/usr/ports/sysutils/u-boot-tools/
/usr/ports/sysutils/u-boot-wandboard/


=3D=3D=3D
Mark Millard
marklmi at yahoo.com



--
Ma= rio.


--
Ma= rio.
--000000000000ac388b0627be7092--