From owner-freebsd-arm@freebsd.org Sun Mar 28 19:13:05 2021 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0A7A75AAECC for ; Sun, 28 Mar 2021 19:13:05 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mx.blih.net (mx.blih.net [212.83.155.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx.blih.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4F7ljD4473z3FsQ; Sun, 28 Mar 2021 19:13:04 +0000 (UTC) (envelope-from manu@bidouilliste.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bidouilliste.com; s=mx; t=1616958782; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=XzmsWQlvOZX4rPQa/xDIaGphT179t6OcZrwiAvy2Ano=; b=ZrX21zcffOPcGyisr8vZBjdtC9ipWtJfBeSecq4hTOHWqB+3hs0AooRd/FgGf5zZZ2vR+r kK7aE+KEM2Hxr7rwC0xbtVXYHDiNMhil2YPw1HIaeOZfB5n+MzjzNax8OLUsGPETCtlquh ql9Z0POXwJK0EvyvEOBRiu0dRveEiOo= Received: from amy (lfbn-idf2-1-644-4.w86-247.abo.wanadoo.fr [86.247.100.4]) by mx.blih.net (OpenSMTPD) with ESMTPSA id 55e08f7c (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Sun, 28 Mar 2021 19:13:02 +0000 (UTC) Date: Sun, 28 Mar 2021 21:13:02 +0200 From: Emmanuel Vadot To: Klaus =?ISO-8859-1?Q?K=FCchemann?= Cc: Klaus =?ISO-8859-1?Q?K=FCchemann?= via freebsd-arm , Ian Lepore Subject: Re: Any good alternative to Raspberry for Arm64? Message-Id: <20210328211302.7410e65c1ba17aecc1daabcd@bidouilliste.com> In-Reply-To: <4F449CAA-F542-4D85-8669-538A8AAF6FF5@googlemail.com> References: <21BE83BC-0667-44F7-83E4-1664A2BC6017@icloud.com> <32656ebc0189f47eb98d538b559fc7a15c6fee37.camel@freebsd.org> <4F449CAA-F542-4D85-8669-538A8AAF6FF5@googlemail.com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.33; amd64-portbld-freebsd14.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4F7ljD4473z3FsQ X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Porting FreeBSD to ARM processors List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Mar 2021 19:13:05 -0000 On Sun, 28 Mar 2021 20:43:57 +0200 Klaus K=FCchemann via freebsd-arm wrote: >=20 > > Am 28.03.2021 um 19:13 schrieb Ian Lepore : > > ?.. Virtually any alternative arm64 system that > > runs freebsd at all is a superior choice over the Rpi family. =20 >=20 > :-), 2 years ago I would have said that you?re right?. the times they are= a changing , scoobidoo... And yet RPI clock support is still non-existant which is required to have proper SoC support for any kind of use (video, audio, any proper spi or i2c support and of power usage reduction etc ...) >=20 > > Anything > > else will have better support from the freebsd developers including, > > especially, the professional developers who are paid by companies to > > support freebsd on arm/arm64. >=20 > your paid colleagues support aarch64 in general, RPI4 is aarch64. And any other SoC benefits from that developement too. > You vastly underestimate your other colleagues who developed special rpi4= -drivers&hacks ! >=20 > > Nobody is paying anybody to support > > freebsd on rpi, and consequently all you get in the way of support is > > half-baked theories and anecdotal reports from other people struggling > > to use an rpi with freebsd. >=20 > Rpi4 is "full-baked?-supported :-) , 8GB RAM, genet, pcie(USB 3.0) , > Supports JTAG, netboot etc. , it never crashed for me the last months/yea= rs. > While some drivers still missing, that?s also the case for other boards. > As a ?power to serve?-cheap-board it`s fully supported, no problems (sinc= e the beginning of the 1st cpu-hack)! lol > > If you're looking to save every penny possible and are willing to put > > up with endless frustration and things not working, get an rpi. If you > > want a usable arm64 computer that runs freebsd, get anything else. > >=20 > you mean the missing documentation-frustration? > While there?s even a little docs available, but e.g. Crowston didn?t need= docs, he used JTAG :-) Ha Ha=20 The day I have to use JTAG to write a driver for one platform is the day I'll stop working on this platform. > For still missing drivers the documentation is in other BSDs or tux.(e.g= . genet -driver was based on other BSD-driver). That's not documentation. I shouldn't have to read Linux source code to write a driver for FreeBSD. > I didn?t save every penny, have RK3388, RK3399 and some other archs, even= Risc-V. > None of the other boards can be considered as ?SMOOTHLY? working because = of paid developers, > Long list of examples available , but that`not the topic. Well, no, it is the topic. > Some people(and developers) didn?t understand the closed source environme= nt of rpi-firmware. ( and other things like u-boot,eeprom)... What is there to understand ? You have blobs, they sometimes works, they sometimes doesn't and since it's closed source there is nothing you can do about it. > That?s why we are here and do support the RPI4 by full-baked theories, an= ecdotal reports, mystical patches and extraordinary configuration-hints. Ha= Ha :-) >=20 > Regards >=20 >=20 > K. >=20 >=20 > _______________________________________________ > 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" --=20 Emmanuel Vadot