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: Sun, 07 Mar 2010 09:41:24 -0600 [thread overview]
Message-ID: <4B93C924.2020600@windriver.com> (raw)
In-Reply-To: <4B9115C5.8070800@esd.eu>
Daniel Gorsulowski wrote:
> Tom wrote:
>> 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
>>
> I just checked out u-boot-arm repository and applied my otc570 patch and Jens
> Scharsigs patch I mentioned above.
> [PATCH ARM] updates the at91 main_clock calculation
> http://lists.denx.de/pipermail/u-boot/2010-February/067779.html
>
> After applying, build runs without errors.
I have applied the lastest version of these patches I could find.
It does build.
There are some compile warnings
soft_i2c.c: In function 'send_reset':
soft_i2c.c:103: warning: unused variable 'pio'
soft_i2c.c: In function 'send_start':
soft_i2c.c:130: warning: unused variable 'pio'
soft_i2c.c: In function 'send_stop':
soft_i2c.c:147: warning: unused variable 'pio'
soft_i2c.c: In function 'send_ack':
soft_i2c.c:166: warning: unused variable 'pio'
soft_i2c.c: In function 'write_byte':
soft_i2c.c:185: warning: unused variable 'pio'
soft_i2c.c: In function 'read_byte':
soft_i2c.c:259: warning: unused variable 'pio'
atmel_dataflash_spi.c:25:2: warning: #warning Please update to use C structur
SoC access !
atmel_usart.c:21:2: warning: #warning Please update to use C structur SoC access !
ohci-at91.c:30:2: warning: #warning Please update to use C structur SoC access
Thanks
Tom
>
> Daniel
>
>>> Best regards,
>>> Daniel Gorsulowski
prev parent reply other threads:[~2010-03-07 15:41 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
2010-03-05 14:31 ` Daniel Gorsulowski
2010-03-07 15:40 ` Tom
2010-03-07 15:41 ` Tom [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=4B93C924.2020600@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