From: John Lenz <lenz@cs.wisc.edu>
To: Pavel Machek <pavel@suse.cz>
Cc: Richard Purdie <rpurdie@rpsys.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: MMC drivers for 2.6 collie
Date: Sun, 14 May 2006 20:37:49 -0500 [thread overview]
Message-ID: <1147657069.5525.12.camel@hydra.domain.actdsltmp> (raw)
In-Reply-To: <20060514162410.GG2438@elf.ucw.cz>
On Sun, 2006-05-14 at 18:24 +0200, Pavel Machek wrote:
> Hi!
>
> > > I've tried searching sharp patches for MMC support, but could not find
> > > it. Or should MMC_ARMMMCI work on collie?
> >
> > Sharp's 2.4 MMC/SD drivers were binary only for all Zaurus models. Since
> > we have documentation on the PXA, a 2.6 driver exists and works for all
> > PXA models as we could guess the power controls and GPIOs. Collie
> > (SA1100 based) used some kind of SPI interface through the LOCOMO chip
> > (as far as I know) which we have no documentation on.
>
> I thought we had completely open-source version at one point?
No, not for the MMC on collie. At least, the patch to the 2.4 kernel
which I based my 2.6 code on did not have any MMC parts, and the
openzaurus distro at the time still included the binary module in the
rom.
IIRC, Chris Larson signed a NDA and got the specs for the MMC device on
collie to develop it for 2.6, but I don't think anything ever came of
it. I also might be remembering he signed a NDA for some other
component, but I think it was the MMC device. Also, the poodle and
collie used different device controllers, so the work will not transfer
over. :(
John
next prev parent reply other threads:[~2006-05-15 1:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 14:53 Pavel Machek
2006-05-14 15:10 ` Richard Purdie
2006-05-14 16:24 ` Pavel Machek
2006-05-15 1:37 ` John Lenz [this message]
2006-05-16 13:47 ` Pavel Machek
2006-05-16 14:35 ` Paulo Marques
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=1147657069.5525.12.camel@hydra.domain.actdsltmp \
--to=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rpurdie@rpsys.net \
/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®