Date: Fri, 14 Feb 2020 20:24:26 +0100 From: Adrian Gassmann <freebsd@x86.ch> To: =?UTF-8?Q?Klaus_K=c3=bcchemann?= <maciphone2@googlemail.com>, Mark Millard <marklmi@yahoo.com>, Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm@freebsd.org Subject: RPI4 vs AMLOGIC s905x2 / x96max Message-ID: <af25439d-fc34-9730-dd48-6ba023c5bdef@x86.ch> In-Reply-To: <7B94C1A8-8523-4993-9074-222358FD5C97@googlemail.com> References: <7E7605DC-021D-448A-8459-8EC26BA9836D.ref@yahoo.com> <7E7605DC-021D-448A-8459-8EC26BA9836D@yahoo.com> <E1j2EmR-000Mwm-ID@iz-wera-new.HS-Karlsruhe.DE> <CACNAnaHVYeuoK=4f7XzokpAVjcqd6ovD58-0LdP_vPGjiXQgdw@mail.gmail.com> <E1j2FRX-000MyR-1O@iz-wera-new.HS-Karlsruhe.DE> <E1j2G3j-000Mzo-Dw@iz-wera-new.HS-Karlsruhe.DE> <CACNAnaHUwu0GmqW9QZRhS2sMK0HpsjdYRz3YouL5FMBdWBCW-Q@mail.gmail.com> <B64C6065-D804-4D6F-8660-F8DBB9946DEB@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> <CACNAnaE-SdeqLKwnodPTFNyWY1sWDNhrt4=5WKjUG_FeH4%2B0-Q@mail.gmail.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <marklmi@yahoo.com>: >> >> >> >> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?af25439d-fc34-9730-dd48-6ba023c5bdef>