From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Ball Subject: Re: [PATCH] dw_mmc: Add Synopsys DesignWare mmc host driver. Date: Thu, 9 Dec 2010 16:01:57 +0000 Message-ID: <20101209160157.GA28586@void.printf.net> References: <20101208115510.GD10998@console-pimps.org> <20101209064751.GA21128@void.printf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from void.printf.net ([89.145.121.20]:46314 "EHLO void.printf.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751749Ab0LIQB6 (ORCPT ); Thu, 9 Dec 2010 11:01:58 -0500 Content-Disposition: inline In-Reply-To: Sender: linux-mmc-owner@vger.kernel.org List-Id: linux-mmc@vger.kernel.org To: Will Newton Cc: Linux Kernel list , linux-mmc@vger.kernel.org, Matt Fleming 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 b= eing > > presented to everyone, without being far too specific? =A0At the mo= ment > > we'd be making x86 desktop users say whether they have this IP, whi= ch > > isn't good. =A0Are the architectures that use this IP already upstr= eam? > > Are they all ARM architectures, for instance? >=20 > I don't know of any architectures upstream that use this IP block. Th= ere is an > SoC from NXP that uses this it but it is not upstream: >=20 > http://ics.nxp.com/support/software/lpc313x.bsp.linux/ >=20 > The architecture we tested and debugged this driver on is not upstrea= m 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 c= omment > if that would be helpful. Sure, sounds good. > > Hm, what's the relationship between NXP and Imagination here? =A0If > > you're submitting a driver with NXP copyright, I think we should ha= ve > > a Signed-off-by line from whomever owns the copyright/wrote that co= de. > > If that's you, that's fine, but it's unclear to me. >=20 > We both have SoCs with this IP block in it, other than that I don't t= hink > there has been any communication between NXP and Imagination about th= is driver. > Hence the lack of SOB from the original authors. >=20 > 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 i= n the code. Okay, makes sense. Thanks, --=20 Chris Ball One Laptop Per Child