From: Remco Poelstra <remco.poelstra@duran-audio.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for LPC2468 from NXP
Date: Thu, 03 Jun 2010 11:39:42 +0200 [thread overview]
Message-ID: <4C07785E.1060900@duran-audio.com> (raw)
In-Reply-To: <20100602100341.899FEAFC6B7@gemini.denx.de>
Hi,
On 02-06-10 12:03, Wolfgang Denk wrote:
>
>> diff --git a/arch/arm/cpu/arm720t/lpc24xx/iap_entry.S b/arch/arm/cpu/arm720t/lpc24xx/iap_entry.S
>> new file mode 100644
>> index 0000000..c31d519
>> --- /dev/null
>> +++ b/arch/arm/cpu/arm720t/lpc24xx/iap_entry.S
>> @@ -0,0 +1,7 @@
>> +IAP_ADDRESS: .word 0x7FFFFFF1
>> +
>> +.globl iap_entry
>> +iap_entry:
>> + ldr r2, IAP_ADDRESS
>> + bx r2
>> + mov pc, lr
>>
> Verbatim copy of arch/arm/cpu/arm720t/lpc2292/iap_entry.S - please
> unify.
>
>
Looking at other architectures for inspiration to solve the above
problem, I find that it's common practice to not-share common code
between SOC's. Is there a reason for that?
Furthermore I see the same problems with some code using direct register
access and other almost identical code using C-structure based access.
Maybe these SOC's are in the same process of getting converted to
C-structures?
Main point: What do you want me to do? I fixed the other minor comments,
so I can send a new patch if you want.
Regards,
Remco Poelstra
next prev parent reply other threads:[~2010-06-03 9:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 7:45 [U-Boot] [PATCH] Add support for LPC2468 from NXP Remco Poelstra
2010-05-12 9:37 ` Wolfgang Denk
2010-05-12 13:01 ` [U-Boot] [PATCH v2] " Remco Poelstra
2010-05-12 13:36 ` Remco Poelstra
2010-05-12 16:09 ` Wolfgang Denk
2010-05-18 7:39 ` Remco Poelstra
2010-05-18 7:53 ` Anatolij Gustschin
2010-05-17 7:11 ` [U-Boot] [PATCH] " Remco Poelstra
2010-05-17 12:21 ` Remco Poelstra
2010-05-21 6:58 ` Remco Poelstra
2010-06-02 8:42 ` Remco Poelstra
2010-06-02 10:03 ` Wolfgang Denk
2010-06-02 11:48 ` Remco Poelstra
2010-06-21 20:08 ` Wolfgang Denk
2010-06-03 9:39 ` Remco Poelstra [this message]
2010-06-08 7:04 ` Remco Poelstra
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=4C07785E.1060900@duran-audio.com \
--to=remco.poelstra@duran-audio.com \
--cc=u-boot@lists.denx.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