Date: Sun, 9 Feb 2020 14:19:56 -0800 From: Bakul Shah <bakul@bitblocks.com> To: mike@karels.net Cc: Warner Losh <imp@bsdimp.com>, freebsd-arm@freebsd.org Subject: Re: RPI4 Install r357606 test 09.02.2020 failed Message-ID: <4551CAE8-08DA-463F-876C-DD1BBAA5D7C5@bitblocks.com> In-Reply-To: <202002092026.019KQXLF021366@mail.karels.net>
index | next in thread | previous in thread | raw e-mail
On Feb 9, 2020, at 12:26 PM, Mike Karels <mike@karels.net> wrote: > >> On Sun, Feb 9, 2020, 1:10 PM <ag@x86.ch> wrote: > >>> ok I understand not all opensource as always claimed Too bad >>> > >> The Raspberry Pi isn't really a totally open design. > >> Warner > > Indeed. In this case, the GPL Linux driver is available as a substitute > for documentation, but it isn't the clearest description of the (5 versions) > of the Ethernet section. Perhaps the plan9 drivers would help? They are considerably simpler and I suspect you mainly want h/w parameters. 9pi (arm) & 9front (arm64) have ethernet, wifi & xhci working. Re: documentation. I asked on their forum about their long promised documentation and was told it is hung up due to some sort of personal issue. The RPF engineers hang out on their forum and they do help provided one asks specific questions. I will be happy to help once I re-bootstrap into freebsd kernel hacking. First I need to figure out why it boots partially and then hangs with repeated controller timeout messages: .... Timecounters tick every 1.000 msec Obsolete code will be removed soon: random(9) is the obsolete Park-Miller LCG f8 usb_needs_explore_all: no devclass mmcsd0: 16GB <SDHC SU16G 8.0 SN 0054AA0F MFG 01/2015 by 3 SD> at mmc0 50.0MHz/4k sdhci_bcm1-slot0: Got command interrupt 0x00030000, but there is no active comm. sdhci_bcm1-slot0: ============== REGISTER DUMP ============== dhci_bcm1-slot0: Sys addr: 0x00000000 | Version: 0x00009902 ... I built -current locally a couple days back and it has the same issue. > > Mike > >>> Zitat von Steve O'Hara-Smith <steve@sohara.org>: >>> >>>> On Sun, 09 Feb 2020 20:49:53 +0100 >>>> ag@x86.ch wrote: >>>> >>>>> >>>>> hello mike thanks for the information. why is this documentation >>>>> not available? is there a conflict between linux and freebsd? >>>> >>>> The Linux port is usually done by the SOC maker, or someone who >>>> signed an NDA with them to get the documentation, and released only as a >>>> compiled kernel. In many ways it is reminiscent of the bad old days of >>>> video acceleration. >>>> >>>> -- >>>> Steve O'Hara-Smith <steve@sohara.org> >>>> _______________________________________________ >>>> freebsd-arm@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-armTo >>>> unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >>> _______________________________________________ >>> 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" >>> >> _______________________________________________ >> 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" > _______________________________________________ > 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"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4551CAE8-08DA-463F-876C-DD1BBAA5D7C5>