From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 7/9] ARM: move exception vectors away from start of binary
Date: Tue, 24 Jan 2012 05:39:43 +0100 [thread overview]
Message-ID: <20120124043943.GT25622@game.jcrosoft.org> (raw)
In-Reply-To: <20120123120738.GB26642@pengutronix.de>
On 13:07 Mon 23 Jan , Sascha Hauer wrote:
> On Mon, Jan 02, 2012 at 04:09:01PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 15:13 Mon 02 Jan , Sascha Hauer wrote:
> > > On Sun, Jan 01, 2012 at 05:37:17AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > On 15:52 Sat 17 Dec , Sascha Hauer wrote:
> > > > > Traditionally U-Boot and barebox have the exception vectors at
> > > > > the start of the binary. There is no real reason in doing so,
> > > > > because in the majority of cases this data will not be at 0x0
> > > > > where it could be used as vectors directly anyway.
> > > > > This patch puts the vectors into a separate linker section and
> > > > > defines an head function which is placed at the start of the
> > > > > image instead. Putting this in a separate function also has
> > > > > the advantage that it can be placed at the start of images
> > > > > which require an additional header like several Freescale i.MX
> > > > > images. As the head function contains the barebox arm magic
> > > > > those images can now also be detected aas barebox images.
> > > > >
> > > > > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > > > > ---
> > > > I've to make it optionnal as on AT91 for boot we must have it at the bigeniing
> > > > of the binary
> > >
> > > Instead of this:
> > >
> > > "b reset\n"
> > > ".rept 7\n"
> > > ".word 0x0\n"
> > > ".endr\n"
> > >
> > > we could do this:
> > >
> > > "b reset\n"
> > > ".rept 7\n"
> > > "1: b 1b\n"
> > > ".endr\n"
> > >
> > > This looks like a exception vector table for the at91 bootloader. BTW
> > > I just looked at a at91 datasheet and at least on the at91sam9260 the
> > > sixth vector should contain the image size to copy. So maybe this does
> > > not work on at91 anyway?
> > I'm working on it so please hold on this
>
> ping. I'd really like to merge the remaining thumb2 support pieces.
I've issue on it
I try to send a version this week sorry but here its chinese new year
Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2012-01-24 4:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 14:52 Thumb-2 support Sascha Hauer
2011-12-17 14:52 ` [PATCH 1/9] ARM i.MX5: prepare to add a imx51_lowlevel_init Sascha Hauer
2011-12-18 14:03 ` Eric Bénard
2011-12-19 10:18 ` Sascha Hauer
2011-12-17 14:52 ` [PATCH 2/9] ARM i.MX51: implement " Sascha Hauer
2011-12-17 14:52 ` [PATCH 3/9] ARM i.MX51 babbage: use generic lowlevel init function Sascha Hauer
2011-12-17 14:52 ` [PATCH 4/9] ARM eukrea i.MX51: use generic lowlevel init Sascha Hauer
2011-12-17 14:52 ` [PATCH 5/9] ARM: update string functions from Linux Kernel Sascha Hauer
2011-12-17 14:52 ` [PATCH 6/9] ARM cache-armv7: use thumb-2 instructions where necessary Sascha Hauer
2011-12-17 14:52 ` [PATCH 7/9] ARM: move exception vectors away from start of binary Sascha Hauer
2011-12-18 23:43 ` Peter Korsgaard
2011-12-20 14:07 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-21 10:09 ` Sascha Hauer
2012-01-01 4:37 ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-02 14:13 ` Sascha Hauer
2012-01-02 15:09 ` Jean-Christophe PLAGNIOL-VILLARD
2012-01-23 12:07 ` Sascha Hauer
2012-01-24 4:39 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2011-12-17 14:52 ` [PATCH 8/9] ARM: get runtime offset of board_init_lowlevel_return by using separate section Sascha Hauer
2011-12-17 14:52 ` [PATCH 9/9] ARM: Allow to compile in thumb-2 mode Sascha Hauer
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=20120124043943.GT25622@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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