From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/9 V4] add new CONFIG_AT91_LEGACY
Date: Sat, 13 Feb 2010 12:12:25 +0100 [thread overview]
Message-ID: <4B768919.9020601@esd.eu> (raw)
In-Reply-To: <4B759857.6070001@windriver.com>
Tom wrote:
> Daniel Gorsulowski wrote:
>> Tom wrote:
>>> Daniel Gorsulowski wrote:
>>>> Hello Tom,
>>>>
>>>> Tom wrote:
>>>>> Jens Scharsig wrote:
>>>>>> * add's the new temporary CONFIG_AT91_LEGACY to all board configs
>>>>>> This will need for backward compatiblity, while change the SoC access
>>>>>> to c structures. If CONFIG_AT91_LEGACY is defined, the deprecated
>>>>>> SoC is used.
...
>> You probably recognized that I did not sent a patch with CONFIG_AT91_LEGACY
>> support but I updated the otc570 board to new SoC access.
>> http://lists.denx.de/pipermail/u-boot/2010-February/067691.html
>> I guess, this is the best solution.
>>
>
> Daniel,
> I still see an error wrt otc570.
>
> Jens,
> I have pushed your patchset of around 2/4 to arm/master.
>
> There will be an error in the otc570 build.
> Tom
>
If you are talking about errors in clock.c, I know about them.
Please take a look at the comments in my otc570 patch. Regarding to Jens
patchset I wrote:
> Apart from a tiny change, I give them an ACK. See
> http://lists.denx.de/pipermail/u-boot/2010-February/067674.html
> and
> http://lists.denx.de/pipermail/u-boot/2010-February/067680.html
Best regards
Daniel Gorsulowski
prev parent reply other threads:[~2010-02-13 11:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 11:03 [U-Boot] [PATCH 1/9 V3] add new CONFIG_AT91_LEGACY Jens Scharsig
2010-01-31 0:57 ` Tom
2010-01-31 11:24 ` [U-Boot] [PATCH 1/9 V3.1] " Jens Scharsig
2010-02-03 21:45 ` [U-Boot] [PATCH 1/9 V4] " Jens Scharsig
2010-02-06 14:19 ` Tom
2010-02-10 11:33 ` Daniel Gorsulowski
2010-02-11 13:56 ` Tom
2010-02-12 6:47 ` Daniel Gorsulowski
2010-02-12 13:08 ` Tom
2010-02-12 18:05 ` Tom
2010-02-13 11:12 ` Daniel Gorsulowski [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=4B768919.9020601@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--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