13:00 <NishanthMenon> paulk: you might be talking of https://github.com/nmenon/omap-u-boot-utils/commit/69b52b618b9c59ec8d2c02fcb85c62481e6e306a been too much time for me to remember the nuances unfortunately :(

13:19 <paulk> NishanthMenon: yep, adding similar delays did the trick :)

16:18 <paulk> NishanthMenon: another thing though, I cannot find any documentation about the device descriptor structure provided as a pointer in the booting parameter structure (for omap3)

16:18 <paulk> is that documentation available?

16:19 <paulk> I'm suspecting the u-boot implementation is not reading it correctly, as raw mmc boot is seen as fat/fs boot here.

17:51 <NishanthMenon> paulk: did you mean configuration header?

17:54 <NishanthMenon> https://github.com/nmenon/omap-u-boot-utils/blob/master/src/gpsign.c ? at least from my ancient slides in https://www.slideshare.net/slideshow/linuxwithoutabootloader/6011635#24

17:55 <NishanthMenon> it probably came in from TRM of that time ..

19:35 <paulk> NishanthMenon: ah sorry I didn't give enough context: I mean the booting parameters provided by the bootrom in r0 to the first-stage bootloader it has loaded

19:35 <NishanthMenon> paulk: aah ok. Sorry, I dont remember :( does'nt TRM give the details?

19:36 <paulk> NishanthMenon: unfortunately no, there is a description of the "booting parameter structure" in table 26-47 of the omap36xx trm but not the "device descriptor structure" that is linked from that previous structure

19:40 <NishanthMenon> paulk: e2e.ti.com might be your best bet.. :(

19:43 <paulk> thanks anyway!

19:58 <NishanthMenon> no problems

20:22 <paulk> so acccording to https://patchwork.ozlabs.org/project/uboot/patch/1311004011-9073-12-git-send-email-aneesh@ti.com/#246852 the information is not available for omap3

20:26 <NishanthMenon> Aaah /me hugs mail archives :)