public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] at91: Get rid of some warnings when building for otc570
Date: Wed, 24 Mar 2010 20:03:50 +0100	[thread overview]
Message-ID: <201003242003.52717.matthias.fuchs@esd-electronics.com> (raw)
In-Reply-To: <20100324120754.CB05D4C022@gemini.denx.de>

> Dear Matthias Fuchs,
> 
> In message <201003241016.20459.matthias.fuchs@esd.eu> you wrote:
> > The soft-i2c code for AT91 defines I2C_SOFT_DECLARATIONS
> > for direct access by dereferencing a pio pointer.
> > The OTC570 platform uses the AT91 gpio API so it does not
> > need the pio variable.
> > 
> > Signed-off-by: Matthias Fuchs <matthias.fuchs@esd.eu>
> > ---
> >  include/configs/otc570.h |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> Applied, thanks.
> 
> So this reduces the warnings to the (pretty common, on AT91):
> 
> 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 !
These are not fixable on-the-fly. As you might know there is a bigger work-in-progress
to switch the AT91 support completely towards c structs. I don't expect this to be done
before the outstanding release.

I am not sure if anyone is working on this right now. If so, please raise your finger!

Matthias

      reply	other threads:[~2010-03-24 19:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24  9:16 [U-Boot] [PATCH] at91: Get rid of some warnings when building for otc570 Matthias Fuchs
2010-03-24 12:07 ` Wolfgang Denk
2010-03-24 19:03   ` Matthias Fuchs [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=201003242003.52717.matthias.fuchs@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.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