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@xxxxxxxxxx> <http://printf.net/> One Laptop Per Child -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
