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: <4D7A50B2.9030603@linaro.org>
Date:	Fri, 11 Mar 2011 16:41:22 +0000
From:	Andy Green <andy@...mcat.com>
To:	Greg KH <greg@...ah.com>
CC:	Linux USB list <linux-usb@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: RFC: Platform data for onboard USB assets

On 03/11/2011 04:36 PM, Somebody in the thread at some point said:

>> Is it true that for on-board devices, it can sometimes be legitimate
>> and useful to be able to deliver platform_data from the board file
>> through to stuff on a USB bus, same as you would for memory mapped,
>> I2C, other busses?
>>
>> Or is that it since it is USB, it can never be useful or legitimate,
>> no matter what different kind of wired-up on-board USB device it is,
>> to have the board definition file configure the driver for that
>> instantiation?
>
> Since it is USB, it is always discoverable, so it doesn't make any sense
> to have this type of thing.
>
> And since your only example was a network device, I think you proved
> your point :)

Well, thanks for the clear answer ^^

Have a nice weekend.

-Andy
--
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/