Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Apr 2021 17:18:19 +0200
From:      =?utf-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com>
To:        Dan Kotowski <dan.kotowski@a9development.com>, freebsd-arm@freebsd.org
Subject:   Re: Any good alternative to Raspberry for Arm64?
Message-ID:  <53D790C4-0CBD-49BC-8D4E-A48C8F9F0E6C@googlemail.com>
In-Reply-To: <Ddcxj7Pgb2JHy5Q-qebjWNQT5DKeFIAAQh85am-X1dSj5MGgPVdsfr35v6wKaPYI_w6_sCKvapke2qD7sZ108muoVVS5vBztVqb8GT6uO_A=@a9development.com>
References:  <21BE83BC-0667-44F7-83E4-1664A2BC6017@icloud.com> <74C08272-D40E-42D2-A623-CEE12C661329@googlemail.com> <f3hHexkIDGQX3sr0f3EOMvUZF0x6JsYpzHZ5bcGch0KxWF3MOakIenD2VfjnJG-JM8SAhlUhDCR_3wZalOKMBGvL4Acyhcl0iO8mdsJDUXs=@a9development.com> <8d54c77b-b5bf-cdc9-7ed5-2bfb6504b388@spth.de> <0434D7DE-14A6-4B78-97C4-508C348DB891@googlemail.com> <vzez0VkHT9Md7U5Nh06Nn6nKDC12DHThVAZh1obdLpsDtbrVYoHcBUXa8M-GKvIv30vxHwNCUbAPNyfi6fFaqksopDIO8hOlMPWVkduSe20=@a9development.com> <9ee70ac3b117b6605ce67102c2864f24a2816d90.camel@freebsd.org> <A3BFAEF0-CD88-4C97-9476-0A8F12481958@yahoo.com> <20210331192030.3fb9314f@kan> <Ddcxj7Pgb2JHy5Q-qebjWNQT5DKeFIAAQh85am-X1dSj5MGgPVdsfr35v6wKaPYI_w6_sCKvapke2qD7sZ108muoVVS5vBztVqb8GT6uO_A=@a9development.com>

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


> Am 01.04.2021 um 16:12 schrieb Dan Kotowski =
<dan.kotowski@a9development.com>:
>=20
> On Wednesday, March 31st, 2021 at 23:20, Alexander Kabaev =
<kabaev@gmail.com> wrote:
>=20
>> On Tue, 30 Mar 2021 17:14:01 -0700
>>=20
>> Mark Millard via freebsd-arm freebsd-arm@freebsd.org wrote:
>>=20
>>> On 2021-Mar-30, at 16:32, Ian Lepore <ian at freebsd.org> wrote:
>>>=20
>>>> On Tue, 2021-03-30 at 22:52 +0000, Dan Kotowski wrote:
>>>>=20
>>>>>> `guess SFP+ would need more special driver-attention ...
>>>>>> from quick reading around the web I guess the DPAA2 also needs a
>>>>>> closed source binary blob.
>>>>>=20
>>>>> So this actually comes from NXP, not SolidRun. Linux already has
>>>>> some/most of what's needed, and the license is GPL-2.0+ OR BSD-3-
>>>>> Clause so there's hope, but I haven't heard a peep from NXP and
>>>>> SolidRun doesn't really have the manpower to port to FreeBSD
>>>>> themselves.
>>>>=20
>>>> =
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/driv=
ers/net/ethernet/freescale/dpaa2/
>>>>=20
>>>> That's actually very good news. If it's dual-licensed it can be
>>>> included in freebsd without any drama. Still needs porting work, or
>>>> maybe it could run using the linuxkpi stuff?
>>>=20
>>> The files there are a mix: a few list just:
>>>=20
>>> SPDX-License-Identifier: GPL-2.0-only
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>>=20
>>> or:
>>>=20
>>> SPDX-License-Identifier: GPL-2.0
>>> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D
>>>=20
>>> or:
>>>=20
>>> // SPDX-License-Identifier: GPL-2.0
>>>=20
>>> or:
>>>=20
>>> /* SPDX-License-Identifier: GPL-2.0 */
>>>=20
>>> ( Kconfig Makefile dpaa2-ptp.[ch] dprtc-cmd.h dprtc.[ch] )
>>>=20
>>> The others (most) list:
>>>=20
>>> // SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
>>>=20
>>> or:
>>>=20
>>> /* SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause) */
>>>=20
>>> The Copyrights seem to be Freescale Semiconductor Inc. and/or
>>> NXP when documented on a file. May be they would be willing
>>> to add the BSD-3-Clause where it is missing?
>>>=20
>>> =3D=3D=3D
>>> Mark Millard
>>> marklmi at yahoo.com
>>> ( dsl-only.net went
>>> away in early 2018-Mar)
>>=20
>> If one does not need to run custom firmware on DPAA2 subsystem, then
>> the only binary blob one needs if an MC firmware which is and always
>> will be the binary-only thing, per our NXP contacts. MC provides
>> intermediate layer API that abstracts hardware configuration at =
somewhat
>> higher level that DPAA from older Layerscape chips did. MC blob is
>> freely downloadable and NXP documents MC and DPAA2 interfaces quite
>> well, but it is a sizable code to write to get things properly
>> integrated. NXP also ships a lot of their low-level code as part of
>> DPDK, which is licensed liberally and can be referenced for the
>> inspiration. Most of fls_dp* files are available there.
>>=20
>> Alexander Kabaev
>=20
> For what it's worth, this SoC is starting to show up in SmartNICs too:
>=20
> =
https://www.xilinx.com/applications/data-center/network-acceleration/alveo=
-sn1000.html
>=20
> I don't have the free cycles or expertise to write/port this code =
myself, but would love to work with someone who does
> _______________________________________________
> freebsd-arm@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to =
"freebsd-arm-unsubscribe@freebsd.org=E2=80=9C


What is this ??   :

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253177

=E2=80=A6.    =
https://gist.github.com/yarshure/1cc3350b4cbd86d7514514b57987b9d7.     =
=E2=80=A6.=20
pcib1: <Generic PCI host controller> on acpi0
pci1: <PCI bus> on pcib1
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver> port 0x20-0x3f mem =
0xa400080000-0xa4000fffff,0xa400504000-0xa400507fff at device 0.0 on =
pci1
ix0: Using 2048 TX descriptors and 2048 RX descriptors
ix0: Using 16 RX queues 16 TX queues
ix0: Using MSI-X interrupts with 17 vectors
ix0: allocated for 16 queues
ix0: allocated for 16 rx queues
ix0: Ethernet address: 90:1b:0e:44:36:0f
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
=E2=80=A6=E2=80=A6



K.




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D790C4-0CBD-49BC-8D4E-A48C8F9F0E6C>