Date: Thu, 24 Sep 2020 10:30:56 -0600 From: Ian Lepore <ian@freebsd.org> To: Oskar Holmlund <oskar.holmlund@yahoo.com>, "mike@karels.net" <mike@karels.net> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: clock problems with BeagleBone Black on 12.2BETA2 Message-ID: <a55e0f0a349cff241ed3773b5b0a39c859ad1c41.camel@freebsd.org> In-Reply-To: <1072725987.651720.1600964732891@mail.yahoo.com> References: <202009222004.08MK4xFj037249@mail.karels.net> <8217af510a451f10ea173bf1e26d04dcd50e8ca6.camel@freebsd.org> <1072725987.651720.1600964732891@mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 2020-09-24 at 16:25 +0000, Oskar Holmlund wrote: > > Den tisdag 22 september 2020 22:13:34 CEST, Ian Lepore < > ian@freebsd.org> skrev: > > > > BB is broken on head right now too, fallout from adding proper > > clock > > drivers recently. I think mmel@ is looking into a fix. > > > > -- Ian > > Do you have any more information about whats broken in head? any use > case? > > I have tested head (r366088) and the clock works for me and assigns > to the hardware that needs clocks like pwm, spi, i2c. > > //Oskar > It was mentioned on irc a few days ago when someone noticed the BBB in the CI setup was failing... <emaste> hrm, looks like BBB has been broken since end of July <emaste> panic: Duplicated clock registration: clk@4_0 <emaste> ah, mmel r363700 <strejda> emaste: im sorry, but this is (unfortunately) expected collateral damage. im aware of this problem but right solution is not trivial and it needs more time. (strejda == mmel@) Then it was mentioned a while later that that BBB is using a very old u-boot, so maybe that has something to do with it. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a55e0f0a349cff241ed3773b5b0a39c859ad1c41.camel>