On Fri, Mar 08, 2013 at 07:39:18AM +0100, Steffen Trumtrar wrote: > On Thu, Mar 07, 2013 at 04:46:25PM -0600, Josh Cartwright wrote: > > On Wed, Mar 06, 2013 at 06:28:50PM +0100, Steffen Trumtrar wrote: > > > On Tue, Mar 05, 2013 at 11:09:29AM -0600, Josh Cartwright wrote: > > [..] > > > > > I have some patches laying around, that have support for booting first stage > > > > > from a SD-Card on a ZedBoard. I didn't send them as of yet, because I'm not > > > > > completely satisfied with them in one or two places. (The clocksource seems to > > > > > be inverse to what barebox expects, which would be a quick fix, and barebox boots > > > > > uuultra slow, if I do everything according to the TRM) > > > > > At the moment, I do not have access to the board though. But I hope I can get a > > > > > hand on it in the next days. > > > > > > > > If you have a chance to send out what you have, I'd be curious to see > > > > it. Fortunately I have several Zynq boards to play with. > > > > > > > > > > Hi! > > > > > > Have a look at > > > http://git.pengutronix.de/?p=str/barebox.git;a=summary > > > > > > I "stole" your clk driver and added it to my patch stack :-) > > > Current state for ZedBoard: > > > - boot first stage from SD-Card > > > - barebox.bin needs to be processed with > > > ./scripts/zynq_checksum barebox.bin BOOT.bin > > > to have the checksum in the BootROM header > > > - clocksource is arm_smp_tmd at seems accurate > > > - the BootROM needs about 4-5 seconds to copy barebox from > > > SD to the OCM. I guess, I need to mess with the SD setup > > > in the BootROM somehow > > > - just enough clkdev to use the timer > > > - all pinctrl, clk setup etc happens in the lowlevel init > > Hi Josh! > > > Hey Steffen- > > > > Thanks for sharing this! I'll be looking to get board support for the > > zc702 on top of your work this weekend (I have several Zynq boards, but > > none of them are ZedBoards). I'm also in the process of porting the > > uboot zynq_gem driver. > > First, \o/. I don't know how the two differ. But I would guess, that > you can pretty much copy the lowlevel stuff et al. > Only the DDR timing stuff may make problems. > > Second: No! Don't! I'm trying to get drivers/net/macb.c running on Zynq. > As far as I can tell at the moment, this is a driver for a > Cadence IP gem. And the zynq uses exactly that IP core. > Alas, I have problems with the dma_alloc_coherent call in its > probe function. Doh! I certainly did not want to duplicate a driver unnecessarily. I'll keep this in mind going forward. > The same goes for the UART driver and other cores. We should not start > developing Xilinx drivers for everything, if in reality we have IP cores > from other providers. Absolutely. Thanks, Josh _______________________________________________ barebox mailing list barebox@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/barebox
