From: George Stefan <stefan.george87@gmail.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: __bss_stop question
Date: Thu, 8 Mar 2012 15:45:59 +0200 [thread overview]
Message-ID: <CAACwSTJQu-mrt+x9=tgipTr+XTPQT+xGqV2zw+NBCfoYn3H=RQ@mail.gmail.com> (raw)
In-Reply-To: <20120308131134.GO12248@game.jcrosoft.org>
[-- Attachment #1.1: Type: text/plain, Size: 968 bytes --]
În data de 8 martie 2012, 15:11, Jean-Christophe PLAGNIOL-VILLARD <
plagnioj@jcrosoft.com> a scris:
> On 14:23 Thu 08 Mar , George Stefan wrote:
> > Hello all,
> > Is __bss_stop the end of barebox.bin?
> > Meaning that, if i have i file which i dd it with offset=768
> > could i refer to it with __bss_stop.
> > Should i consider also the bareboxenv, meaning that
> > the end of barebox.bin is __bss_stop + sizeof(bareboxenv)?
> > PS: board is imx53 loco
> the env is where you want
>
> and barebox_image_size will give you the size of barebox
>
> and the end of barebox is __bss_start
>
> Best Regards,
> J.
>
Thanks for the reply.
So, if i do something like
dd if=barebox.bin of=/dev/mmcblk0 bs=512 && sync\
and
dd if=uImage of=/dev/mmcblk0 bs=512 seek=768 && sync
how could i access the contents of uimage within barebox?
Since " the end of barebox is __bss_start" should it be __bss_start?
Regards,
George!
[-- Attachment #1.2: Type: text/html, Size: 1526 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2012-03-08 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 12:23 George Stefan
2012-03-08 13:11 ` Jean-Christophe PLAGNIOL-VILLARD
2012-03-08 13:45 ` George Stefan [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='CAACwSTJQu-mrt+x9=tgipTr+XTPQT+xGqV2zw+NBCfoYn3H=RQ@mail.gmail.com' \
--to=stefan.george87@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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