From: Masahiro Yamada <yamada.m@jp.panasonic.com>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [Question] How was zedboard lowlevel written?
Date: Tue, 13 Jan 2015 14:17:49 +0900 [thread overview]
Message-ID: <20150113141749.CAC9.AA925319@jp.panasonic.com> (raw)
In-Reply-To: <73d26o7251.fsf@dude.hi.pengutronix.de>
Hi Steffen,
On Fri, 09 Jan 2015 10:07:54 +0100
Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote:
>
> Hi!
>
> Masahiro Yamada writes:
> > Hello Steffen Trumtrar,
> >
> > I am seeing arch/arm/boards/avnet-zedboard/board.c
> > written by you.
> >
>
> Sadly it's been a while since I touched this :(
>
> > Is this file equivalent to ps7_init.c spit by Xilinx tool?
> > Or did you write it by hand from scratch ? (I doubt it.)
> >
> >
> > I have ZC706, another Zynq board.
> > If I could port barebox to this board, that would be great!
> > But I am just worndering whether I could get your advice about
> > how to create the lowlevel file.
> >
>
> The lowlevel.c/flash_header.c are adapted from the ps7_init code IIRC.
> Xilinx uses a prebootloader and a bootloader for the Zynq, barebox does
> not. So you would have to put all values into the respective two files.
> And you need to run scripts/zynq_mkimage for the checksum (but I think
> the Makefile already does that).
>
> I wish I could be of more help here, but I can't really remember the
> actual steps necessary and I don't have a ps7_init handy at the moment.
>
OK, thanks.
I just wanted to be sure in case there were some tools or tips etc.
that would save my time.
Anyway, I will give it a try.
Best Regards
Masahiro Yamada
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-01-13 5:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 10:47 Masahiro Yamada
2015-01-09 9:07 ` Steffen Trumtrar
2015-01-13 5:17 ` Masahiro Yamada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150113141749.CAC9.AA925319@jp.panasonic.com \
--to=yamada.m@jp.panasonic.com \
--cc=barebox@lists.infradead.org \
--cc=s.trumtrar@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox