LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Will Newton <will.newton@gmail.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-mmc@vger.kernel.org, Matt Fleming <matt@console-pimps.org>
Subject: Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver.
Date: Thu, 9 Dec 2010 16:01:57 +0000 [thread overview]
Message-ID: <20101209160157.GA28586@void.printf.net> (raw)
In-Reply-To: <AANLkTimMgrawcndvUTYYjq9BGFqs-sbRsZkwVQ0Uvhvb@mail.gmail.com>
Hi Will,
On Thu, Dec 09, 2010 at 12:11:06PM +0000, Will Newton wrote:
> > Is there something we could depend on that would stop this driver being
> > presented to everyone, without being far too specific? At the moment
> > we'd be making x86 desktop users say whether they have this IP, which
> > isn't good. Are the architectures that use this IP already upstream?
> > Are they all ARM architectures, for instance?
>
> I don't know of any architectures upstream that use this IP block. There is an
> SoC from NXP that uses this it but it is not upstream:
>
> http://ics.nxp.com/support/software/lpc313x.bsp.linux/
>
> The architecture we tested and debugged this driver on is not upstream either
> unfortunately. :-/
Okay. I think "depends on ARM" is appropriate for now, and we could
expand that later if the block appears in a MIPS SoC or something.
Does that work for you?
> The driver is available at the link above, I can add the URL to the comment
> if that would be helpful.
Sure, sounds good.
> > Hm, what's the relationship between NXP and Imagination here? If
> > you're submitting a driver with NXP copyright, I think we should have
> > a Signed-off-by line from whomever owns the copyright/wrote that code.
> > If that's you, that's fine, but it's unclear to me.
>
> We both have SoCs with this IP block in it, other than that I don't think
> there has been any communication between NXP and Imagination about this driver.
> Hence the lack of SOB from the original authors.
>
> The driver is available publically under the GPL, so it was my
> understanding that
> no SOB was required as long as we keep appropriate copyright credit in the code.
Okay, makes sense. Thanks,
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2010-12-09 16:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-06 15:53 [RESEND PATCH] " Will Newton
2010-12-08 11:55 ` Matt Fleming
2010-12-08 13:14 ` Will Newton
2010-12-08 14:21 ` [PATCH] " Will Newton
2010-12-08 16:07 ` Matt Fleming
2010-12-09 6:47 ` Chris Ball
2010-12-09 12:11 ` Will Newton
2010-12-09 16:01 ` Chris Ball [this message]
2010-12-09 17:24 ` Will Newton
[not found] ` <20101211192320.GA24430@void.printf.net>
2010-12-12 8:41 ` Russell King - ARM Linux
2010-12-12 11:15 ` Russell King - ARM Linux
2010-12-12 10:57 ` Will Newton
2010-12-12 13:52 ` Chris Ball
2010-12-12 14:03 ` Will Newton
2010-12-12 14:11 ` Russell King - ARM Linux
2010-12-12 14:31 ` Will Newton
2010-12-12 14:47 ` Russell King - ARM Linux
2010-12-12 15:17 ` Will Newton
2010-12-16 17:04 ` [PATCH v4] " Will Newton
2011-01-02 6:20 ` Chris Ball
2011-01-18 7:54 ` Jaehoon Chung
2011-01-18 10:21 ` Will Newton
2011-02-08 6:38 ` Jaehoon Chung
2011-02-08 10:29 ` Will Newton
2011-02-08 10:49 ` Jaehoon Chung
2011-02-08 12:06 ` Will Newton
2010-12-09 17:35 ` [PATCH] " Chris Ball
2010-12-09 17:46 ` Will Newton
-- strict thread matches above, loose matches on Subject: below --
2010-11-29 17:35 Will Newton
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=20101209160157.GA28586@void.printf.net \
--to=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=will.newton@gmail.com \
--subject='Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver.' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).