linux-kernel - Re: RFC: Platform data for onboard USB assets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110317213245.GB16065@kroah.com>
Date:	Thu, 17 Mar 2011 14:32:45 -0700
From:	Greg KH <greg@...ah.com>
To:	Nicolas Pitre <nicolas.pitre@...aro.org>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Arnd Bergmann <arnd@...db.de>, andy.green@...aro.org,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On Thu, Mar 17, 2011 at 05:03:17PM -0400, Nicolas Pitre wrote:
> On Thu, 17 Mar 2011, Greg KH wrote:
> 
> > On Wed, Mar 16, 2011 at 10:14:01PM -0400, Nicolas Pitre wrote:
> > > > What drivers need this?  Specifics please.
> > > 
> > > Let me quote Arnd Bergmann:
> > > 
> > > |I have just verified with my Pandaboard that the pins on the SMSC9514
> > > |usb ethernet that are meant to be connected to a serial EEPROM are
> > > |indeed not connected anywhere.
> > > 
> > > > Anyway, specifics are the best way forward if anyone has such a messed
> > > > up system.
> > > 
> > > PandaBoards are becoming quite popular.
> > 
> > I have one right here.
> > 
> > But can't this device be detected by the usb device id and the quirk
> > added that way?  Like all other "odd" USB devices are currently handled?
> 
> It is not the device which is odd, but rather the environment in which 
> it is being used for this specific case.  I'd expect to see the same 
> SMSC9514 chip also used in off-the-shelf USB-to-Ethernet dongles with no 
> quirks needed.
> 
> However, a different part of the kernel knows already perfectly well 
> when it is actually running on that specific board.  Hence the desire to 
> come up with a mechanism allowing to tell the driver about a quirk for 
> the particular device instance on this board without having to do the 
> heavy round trip through user space.

It's not "heavy" at all, as it happens today, for every device found in
the system.

Again, we have this infrastructure to do this, in place, for this very
reason, why else would we have created it, to ignore it?

Anyway, as stated before, if someone has a specific patch for the
pandaboard, send it on, and I'll consider it.  Extra bonus points for
curse words describing the hardware people who are causing this to be
required.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/