mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rob Emanuele <poorarm@shoreis.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>,
	Andrew Victor <avictor.za@gmail.com>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-kernel@vger.kernel.org, drzeus-mmc@drzeus.cx
Subject: Re: [PATCH 2/6] Unified AVR32/AT91 MCI Platform Driver
Date: Mon, 15 Jun 2009 11:04:28 -0700	[thread overview]
Message-ID: <c8284b5b0906151104j204b8b96j7248d20fb7498f82@mail.gmail.com> (raw)
In-Reply-To: <4A366FFA.80700@atmel.com>

Nicolas,

>> +config AT91_2MMC
>> +     bool "Use both MMC Ports"
>> +     depends on MACH_AT91SAM9G20EK
>> +     help
>> +       Select this if you have connected both MMC Slots.  Answer No if unsure.
>> +
>
> Well I do not like this configuration addition. If it is created
> to differencing your custom board with the -EK, we will have to
> consider something else.
>

Why don't I build out a patch for a new board that demonstrates using
the atmel_mci on the AT91?  I'll call it something like
board-sam9g20-ek-2slot-mod.c.  I may have mentioned that Atmel's rev D
of this board has both slot already on it but they don't know when its
going to production.  They still have to sell out of rev B and C.

In related news, I have a small number of adapter boards that I'm
using bring MCI Slot A to a micro sd slot on the AT91SAM9G20-EK.  They
also fit the AT91SAM9XE-EK and possibly others.  If you or anyone else
is working on this patch set and would like to test with both slots I
can send a few of them out.

Thanks,

Rob

  reply	other threads:[~2009-06-15 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-13  0:59 Rob Emanuele
2009-06-15 15:59 ` Nicolas Ferre
2009-06-15 18:04   ` Rob Emanuele [this message]
2009-06-15 16:35 ` Nicolas Ferre

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=c8284b5b0906151104j204b8b96j7248d20fb7498f82@mail.gmail.com \
    --to=poorarm@shoreis.com \
    --cc=avictor.za@gmail.com \
    --cc=drzeus-mmc@drzeus.cx \
    --cc=haavard.skinnemoen@atmel.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    /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

all inboxes | Powered by JetHome®