Date: Tue, 3 Mar 2020 21:27:11 +0100 From: Bernd Walter <ticso@cicely7.cicely.de> To: Klaus =?iso-8859-1?Q?K=FCchemann?= <maciphone2@googlemail.com> Cc: Emmanuel Vadot <manu@bidouilliste.com>, freebsd-arm@freebsd.org, Bernd Walter <ticso@cicely7.cicely.de> Subject: Re: RockPro64 with u-boot 2010.01 Message-ID: <20200303202711.GR52462@cicely7.cicely.de> In-Reply-To: <AB60C1C3-2888-496E-A6CE-D6F7C80D296A@googlemail.com> References: <20200302225606.GN52462@cicely7.cicely.de> <20200303141931.365fb9b9c85339190b7c405a@bidouilliste.com> <454BC07B-A0B5-467C-8682-00BE291D4CB7@googlemail.com> <20200303173349.bd9b69669633b048bbed107b@bidouilliste.com> <5F875EA0-E86A-4EF2-B4EF-0B07E166BA3D@googlemail.com> <20200303172801.GQ52462@cicely7.cicely.de> <4DA153F5-219A-4C5B-91DE-1F6C04DBA482@googlemail.com> <20200303191748.d28e64b2ee200ed9edc9abc7@bidouilliste.com> <AB60C1C3-2888-496E-A6CE-D6F7C80D296A@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 03, 2020 at 08:12:57PM +0100, Klaus Küchemann wrote: > > > > Am 03.03.2020 um 19:17 schrieb Emmanuel Vadot <manu@bidouilliste.com>: > > > > On Tue, 3 Mar 2020 18:55:57 +0100 > > Klaus Küchemann <maciphone2@googlemail.com> wrote: > > > >> > >> > >>> Am 03.03.2020 um 18:28 schrieb Bernd Walter <ticso@cicely7.cicely.de>: > >>> > >>> On Tue, Mar 03, 2020 at 05:58:22PM +0100, Klaus Küchemann wrote: > >>>> > >>>> ??.. > >>> > >>> Ok - there are two likely unrelated issues. > >>> First is that my self build u-boot 2020.01 didn't boot and your > >>> build worked fine. > >>> > >> The problem is that when the u-boot ports-maintainer begins to talk about > >> the distance of the sun to earth, I answer with IceCream , > >> and he replies with talking about his new shaver :-) Ha Ha > >> So probably a language barrier of both of us .. > > > > ??? > > > >> So we could not make a ?deal? for upgrading the fbsd-u-boot-port to it`s current version so far? > > > > You reached out to me privately to say that you wanted to update the > > u-boot port, I told you that there will be problem with rockchip but > > that you should try to update the ports. Your response was that you > > will not do that because you didn't wanted to "disturb my workflow" and > > "steal my time" and that I'm the "u-boot man" or whatever. > > If you want to update u-boot, please send patches and make sure that > > everything is working on most of the boards that we support. If you > > don't have a lot of boards reach out to people for a call or testing. > > I'll also note that you've never compiled u-boot from our ports tree, > > I don't know if you ever compiled u-boot since you've talked about the > > openbsd port, > > Yes, I told you that we probably should think about backporting patches > (for e.g. ATF) but that I don???t like to backport to 2019.10 , > and instead would prefer to back port to 2020.01 > Because why patching ???old" versions when the upstream is already patched? > You can ask Bernd : > There is no more reboot-issue with Rockchip with the version I???ve uploaded to the Wiki . > You told me that you don???t want to upgrade to 2020.01.. I can't say if there had been reboot issues, but it does reboot with your 2020.10 u-boot binary. Also I can have the RX line connected which was a problem with the older u-boot. > > > and their ATF contain some patches for rockchip which > > makes me think again that an ATF update is needed (but haven't had time > > yet to try myself). > > Why waiting for months or so until they update if that???s manageable by a backport-patches? > I don???t want to patch all updates from "MacOS 10.15.3 to MacOS 9.2.2??? ;-) Maybe because he had no time to try himself yet? It is for current after all. > >>> Then there is the USB card reader problem within FreeBSD, > >>> which I hadn't when I booted the very same system with the > >>> u-boot 2019.10, which I installed via package on my 12.1 amd64. > >>> Maybe the 2G vs 4G RAM avoided triggering the bug - who knows. > >>> I just mentioned it in the same thread since it happened to me after > >>> using the newer u-boot (and therefor the full 4G RAM). > >>> > >>> -- > >>> B.Walter <bernd@bwct.de> http://www.bwct.de > >>> Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > >> > >> At the moment I can only say that the card reader-panic has nothing to do with the 4GB Ram itself, but as you suspect, it perhaps could have to do with what the fbds-kernel is ?doing? with that additionally 2 Gigs? > >> I?ll give it GENERIC-MMCCAM and then I?ll look if the issue consists... > > > > I don't see how MMCCAM will help for an usb card reader. > > Also dwmmc doesn't have MMCCAM code so you will not able to boot from > > SD. > > > > -- > > Emmanuel Vadot <manu@bidouilliste.com> > What I meant is: I compile to src-head from TODAY(to whatever kernel), because if`ve seen many issues in that range the last weeks, which were solved(perhaps even by you) but other issues came new to head??? > ( e.g. RPI4 booted again but suddenly only 1 CPU is detected) > > But what I definitely can say is that the card reader- panic has nothing to do with any ATF-patch, > wherever ATF was patched. It is not a show stopper for me. The reason I bought the board was to have a 4G system to compile. And my typical setup is having two microSD cards as mirrored ZFS. If I find time, I will design a PCB to add a second uSD slot for the Pine64 and Rockpro64. The eMMC, as well as the WiFi module connector, should both have the required signals. I do miss erase support via USB reader. Having two uSD slots is what I like with the Wandboards, but those are 32-bit. > So for the moment my question is : what causes 2020.01 to panic where???s Bernd`S 2019.10 > Doesn???t crash??? perhaps you know why, > until I know that > of course I will not send patches??? I don't get the rationale behind this statement... -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200303202711.GR52462>