public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] AVR32 removal due to lack of custodian.
Date: Mon, 27 Feb 2012 14:36:10 +0100	[thread overview]
Message-ID: <4F4B86CA.8000301@gmail.com> (raw)
In-Reply-To: <201202271409.00612.marex@denx.de>

Hi Marek,

On 27.02.2012 14:09, Marek Vasut wrote:

>> I'm willing to get u-boot avr32 support to live on for at least some
>> years, if no one else volunteers.
>>

> that'd be great! There's especially one problem I found with the AVR32 stuff. 
> The MMC driver. I take it the "gen_atmel_mci.c" driver can be used instead of 
> "atmel_mci.c", which uses the legacy MMC API? Can you flip the AVR32 boards to 
> the new MMC driver so we can drop the legacy MMC API any soon please?

Sven posted patches [1] some days ago which are almost working. That
series have some timing issues which should be fixed inside the mmc
framework, see [2] for more information on that.

I will rework these patches next days and do some testing. Would be
great to get a comment on [2] from Andy Fleming (as MMC custodian).

regards

Andreas Bie?mann

[1] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/112056
[2] http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/112421

  reply	other threads:[~2012-02-27 13:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25 22:13 [U-Boot] [PATCH] AVR32 removal due to lack of custodian Wolfgang Denk
2012-02-25 22:38 ` Jerry Van Baren
2012-02-27  1:05 ` Paul Gortmaker
2012-02-27 11:25 ` Andreas Bießmann
2012-02-27 13:09   ` Marek Vasut
2012-02-27 13:36     ` Andreas Bießmann [this message]
2012-02-27 13:37       ` Marek Vasut
2012-03-04 20:55   ` Wolfgang Denk
2012-03-06 12:49     ` Hans-Christian Egtvedt

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=4F4B86CA.8000301@gmail.com \
    --to=andreas.devel@googlemail.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