On Wed, Sep 22, 2021 at 4:28 AM Vaittinen, Matti <Matti.Vaittinen@xxxxxxxxxxxxxxxxx> wrote: > > On 9/21/21 19:40, H. Nikolaus Schaller wrote: > > Hi Matti, Tony, > > > >> Am 21.09.2021 um 18:07 schrieb Suman Anna <s-anna@xxxxxx>: > >> > >> Hi Matti, Tony, > >> > >> On 9/21/21 2:47 AM, Tony Lindgren wrote: > >>> * Matti Vaittinen <mazziesaccount@xxxxxxxxx> [210920 08:23]: > >>>> Finally, adding the udelay(100); (as Tony suggested) at the end of the > >>>> omap_reset_deassert() did make the oops go away even when pruss_tm was > >>>> enabled. I don't know what would be a proper fix though. > >> > >> I have been able to boot v5.15-rc1 just fine on my BBB without any additional > >> changes [1]. > > > > Same for me with a v5.15-rc1 based kernel. > > > >> May I ask what is your BBB board version? My board is rev.A5C. > > > > I have an Rev B6 with EXP41 display attached. I think Matti reported a Rev C board? > > Oops. Yes I did. I _thought_ I have Rev-C (3?) boards. Not exactly sure > why I think so - perhaps that was what I ordered... And I really think > the ones connected to automated test setup at the office are Rev-C. > > Now that I tried to verify this - The one which I used to reproduce this > issue (and now verify the patch from Tony) at home, seems to have say > "PCB Rev6B" on PCB. However the u-boot says: > > => printenv board_rev > board_rev=00C0 > => > > but I have no idea where the environment variable comes from... > > Maybe a stupid question - how to find out the exact revision? Run: hexdump -e '8/1 "%c"' /sys/bus/i2c/devices/0-0050/eeprom -n 28 | cut -b 5-28 Then lookup: https://github.com/beagleboard/image-builder/blob/master/readme.md Regards, -- Robert Nelson https://rcn-ee.com/
