From: bones@secretlab.ca (John Bonesio)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM:boot:device tree: Allow the device tree binary to be appended to zImage
Date: Mon, 21 Mar 2011 16:42:24 -0700 [thread overview]
Message-ID: <4D87E260.6050902@secretlab.ca> (raw)
In-Reply-To: <alpine.LFD.2.00.1103211844500.11889@xanadu.home>
Hi Nicolas,
Is this addhi instruction the only one, or do I need to go through and
find other instructions to update as well?
Thanks for being patient as I learn.
- John
On 03/21/2011 03:49 PM, Nicolas Pitre wrote:
> On Mon, 21 Mar 2011, John Bonesio wrote:
>
>> This patch provides the ability to boot using a device tree that is appended
>> to the raw binary zImage (e.g. cat zImage <filename>.dtb > zImage_w_dtb).
>>
>> Signed-off-by: John Bonesio <bones@secretlab.ca>
>
> One minor glitch still... ;-)
>
>> @@ -288,12 +344,28 @@ wont_overwrite:
>>
>> /*
>> * Relocate all entries in the GOT table.
>> + * Bump bss entries to _edata + dtb size
>> */
>> 1: ldr r1, [r11, #0] @ relocate entries in the GOT
>> - add r1, r1, r0 @ table. This fixes up the
>> - str r1, [r11], #4 @ C references.
>> + add r1, r1, r0 @ This fixes up C references
>> + cmp r1, r2 @ if entry >= bss_start &&
>> + cmphs r3, r1 @ bss_end > entry
>> + addhi r1, lr @ entry += dtb size
>
> Some toolchains won't accept this shortened version unless you compile
> for Thumb. You should instead use:
>
> addhi r1, r1, lr
>
> Otherwise...
>
> Reviewed-by: Nicolas Pitre <nicolas.pitre@linaro.org>
>
>
> Nicolas
next prev parent reply other threads:[~2011-03-21 23:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 22:19 [PATCH v2] ARM:boot:device tree: Allow the device tree binary to be appended to zImage John Bonesio
2011-03-21 22:49 ` Nicolas Pitre
2011-03-21 23:42 ` John Bonesio [this message]
2011-03-22 16:47 ` Nicolas Pitre
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=4D87E260.6050902@secretlab.ca \
--to=bones@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).