From: Tom <Tom.Rix@windriver.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/1] AT91: Update otc570 board to new SoC access
Date: Fri, 05 Mar 2010 08:14:28 -0600 [thread overview]
Message-ID: <4B9111C4.1000904@windriver.com> (raw)
In-Reply-To: <4B910C4F.5020404@esd.eu>
Daniel Gorsulowski wrote:
> Hello Tom
>
> Daniel Gorsulowski wrote:
>> * convert otc570 board to use c stucture SoC access
>> * change gpio access to at91_gpio syntax
>>
>> Signed-off-by: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
>> ---
>> This patch requires Jens Scharsigs new SoC access patchset.
>> http://lists.denx.de/pipermail/u-boot/2010-February/067424.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067425.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067426.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067427.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067428.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067429.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067430.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067431.html
>> http://lists.denx.de/pipermail/u-boot/2010-February/067432.html
>>
> ...
>
> I recognized, you didn't apply this patch yet. Is there any reason, or did you
> simply slip this patch?
>
> Btw. I'm also missing this patch:
> http://lists.denx.de/pipermail/u-boot/2010-February/067779.html
>
Yes.
This was slipped.
I spent some time trying to work out which patches needed to be
applied to remove the build errors I was seeing with otc but
was unable to.
Please send me the list of patches and oder of application.
Tom
> Best regards,
> Daniel Gorsulowski
next prev parent reply other threads:[~2010-03-05 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 13:57 [U-Boot] [PATCH 1/1] AT91: Update otc570 board to new SoC access Daniel Gorsulowski
2010-03-05 13:51 ` Daniel Gorsulowski
2010-03-05 14:14 ` Tom [this message]
2010-03-05 14:31 ` Daniel Gorsulowski
2010-03-07 15:40 ` Tom
2010-03-07 15:41 ` Tom
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=4B9111C4.1000904@windriver.com \
--to=tom.rix@windriver.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