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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 11 Mar 2011 11:37:10 -0800
From:	Greg KH <greg@...ah.com>
To:	andy.green@...aro.org
Cc:	Alan Stern <stern@...land.harvard.edu>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Arnd Bergmann <arnd@...db.de>,
	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On Fri, Mar 11, 2011 at 06:09:19PM +0000, Andy Green wrote:
> >Also, do you have a real example of a USB driver today that needs this?
> 
> I think you find without devpath -> platform_data mapping, the kind
> of layout given above is made quite difficult to support in Linux.

So you have devices today that you can not support in Linux because of
this problem?  Please provide us specifics about them and we will gladly
work to solve this.  But without such information, hand-waving is going
to get you nowhere.

> Saying, "oh go away and do it in userspace" actually means special
> scripts that grep /proc/cpuinfo to reproduce the knowledge inherent
> already in the board definition file, although it's out of your hair
> nicely, it leaves me feeling we reached an overall solution that is
> "less good than it should be".

I'm saying "do network device naming in userspace" as that is where it
belongs.

If you have other type of configuration you need to do, again, provide
us specifics please and we will be glad to work on the proper solution.

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/