From owner-freebsd-arm@freebsd.org Fri Feb 14 19:24:31 2020 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 993CC23F192 for ; Fri, 14 Feb 2020 19:24:31 +0000 (UTC) (envelope-from freebsd@x86.ch) Received: from einstein.sui-inter.net (einstein.sui-inter.net [80.74.145.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.sui-inter.net", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48K3Gk5JRbz44Q8 for ; Fri, 14 Feb 2020 19:24:30 +0000 (UTC) (envelope-from freebsd@x86.ch) Received: from [172.20.10.5] (unknown [213.55.225.23]) by einstein.sui-inter.net (Postfix) with ESMTPSA id CF513B1C047C; Fri, 14 Feb 2020 20:24:27 +0100 (CET) Received-SPF: pass (einstein.sui-inter.net: connection is authenticated) Subject: RPI4 vs AMLOGIC s905x2 / x96max To: =?UTF-8?Q?Klaus_K=c3=bcchemann?= , Mark Millard , Emmanuel Vadot , freebsd-arm@freebsd.org References: <7E7605DC-021D-448A-8459-8EC26BA9836D.ref@yahoo.com> <7E7605DC-021D-448A-8459-8EC26BA9836D@yahoo.com> <36CF6E4B-5607-4752-B2DF-C265BCFB95BA@yahoo.com> <1BE59567-E669-4A88-8389-2E321B0AC1AE@yahoo.com> <27BE7BAF-FD2C-41C6-B270-4BAF77D1FB0C@yahoo.com> <7465BC0D-3F4C-4CD9-B614-0DF321C94331@yahoo.com> <876C4DBE-A243-425A-9978-209C24387668@yahoo.com> <32D0E068-2E1E-46AA-A907-7974BF4DC46D@yahoo.com> <2DC3F5F2-11EB-44A4-BC45-F5A1E92B509B@googlemail.com> <3333F8A8-591F-4722-9E63-904414974142@yahoo.com> <7B94C1A8-8523-4993-9074-222358FD5C97@googlemail.com> From: Adrian Gassmann Message-ID: Date: Fri, 14 Feb 2020 20:24:26 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0 MIME-Version: 1.0 In-Reply-To: <7B94C1A8-8523-4993-9074-222358FD5C97@googlemail.com> X-Rspamd-Queue-Id: 48K3Gk5JRbz44Q8 X-Spamd-Bar: +++ Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of freebsd@x86.ch has no SPF policy when checking 80.74.145.25) smtp.mailfrom=freebsd@x86.ch X-Spamd-Result: default: False [3.91 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; RECEIVED_SPAMHAUS_PBL(0.00)[23.225.55.213.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.11]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; TO_DN_SOME(0.00)[]; IP_SCORE(0.27)[ipnet: 80.74.144.0/20(0.80), asn: 21069(0.53), country: CH(0.04)]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_NA(0.00)[x86.ch]; AUTH_NA(1.00)[]; RWL_MAILSPIKE_GOOD(0.00)[25.145.74.80.rep.mailspike.net : 127.0.0.18]; URI_COUNT_ODD(1.00)[3]; NEURAL_SPAM_MEDIUM(0.84)[0.840,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_SPAM_LONG(1.00)[0.999,0]; R_SPF_NA(0.00)[]; FREEMAIL_TO(0.00)[googlemail.com]; RCVD_IN_DNSWL_LOW(-0.10)[25.145.74.80.list.dnswl.org : 127.0.5.1]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:21069, ipnet:80.74.144.0/20, country:CH]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; FROM_EQ_ENVFROM(0.00)[] Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2020 19:24:31 -0000 the rpi4 is not interesting in terms of price the x96max USB 3 Received 1000MBPS Man today for $ 30 invest better there Am 14.02.2020 um 16:32 schrieb Klaus Küchemann via freebsd-arm: > >> Am 14.02.2020 um 12:20 schrieb Mark Millard : >> >> >> >> For the root cause identification, you are welcome. >> >> (I've not proposed a solution for FreeBSD to adopt.) >> > But THE SKULL( ..just kidding,,) has( proposed a solution for FreeBSD) :-) … …. : >> Am 14.02.2020 um 11:10 schrieb Emmanuel Vadot : >> >> On Fri, 14 Feb 2020 10:54:40 +0100 >> >> I have hold off the upgrade to 2020.01 as rockchip u-boot needs a >> newer ATF and they didn't made a new release yet. My plan is to wait >> until 2020.04 is release and if at that time there is still no new ATF >> release just update the ports to use the latest git version. > > It couldn’t be clearer: > NO breakage for Rockchip as long as there is no usptream - RELEASE. > The only thing possible Manu could think about is backporting, > but of course only from the upstream and NOT from any hacks outside there. > Backporting is much work and perhaps not the way he wants to go, so it is to be accepted > to wait for 2020.04 . > > >> Mark Millard :… I also do not see a communication path for the size to be reported >> to u-boot so that it could automatically adjust. > The communication-path is to track the u-boot upstream first. > If manu wouldn't do that, he would get complaints > for shutting down my RockPro64 ;-) > > Nevertheless, Mark, thanks again investigating to retrack the root cause of RPI4 breakage. > And all that u-boot stuff is absolutely no reason to stop support the RPI4(if possible), > Just hook up your RPi4-version which boots and continue patching that messy gadget. > But please in the (fbsd-) upstream ... > > just my two cents > > Regards > > Klaus > > _______________________________________________ > 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"