> On Mar 8, 2017, at 12:34 AM, Sam Ravnborg <sam@xxxxxxxxxxxx> wrote: > > Hi Andrey. > > On Mon, Mar 06, 2017 at 02:53:11PM -0800, Andrey Smirnov wrote: >> Hi everyone, >> >> I recently had a chance to work with at91sam9x5ek board and as a part >> of that effort I converted the code to support features found in >> Barebox for i.MX based SoCs. Most notably this patchset converts >> at91sam9x5ek to use multi-image PBL build process as well as adds >> support for board initialization from attached devicetree blob. > > Impressive series - looks good! And timing was good. > > I have a proprietary at91sam9263 based bord that is familiar > with the 9263 evaluation kit. > The current bootloader is latest bootstrap + an ancient U-Boot. > As we have another board (i.MX6 based) there is some synergy into > using the same bootloader on both boards. > > Can you give any hints on what needs to be done on top of > your patch-set to support the 9263 evalutation kit? > > When booting from an SD-Card/NOR-Flash/USB would I then need > to use at91bootstrap, or can I use only barebox? > > If I move forward with this and I can find an 9263 > evaluation kit I would then also update this. On 9263 the sram is huge so you can build barebox as first stage I add this a long time ago on usb_a9263_bootstrap_defconfig or other (all the EK). This will build a barebox that can load you image from multiple source in a sequence and then use a std barebox To switch to DT you will have to import the DT I did for the kernel and replace the hw i2c by a i2c gpio as the i2c IP on at91 has a lot of quirks and for barebox it will not make sense to port it Best Regards, J. _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
