linux-kernel - Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform

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:	Sun, 13 Mar 2011 17:13:31 +0000
From:	Andy Green <andy@...mcat.com>
To:	Greg KH <greg@...ah.com>
CC:	"Rafael J. Wysocki" <rjw@...k.pl>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org, patches@...aro.org
Subject: Re: [RFC PATCH 3/4] PLATFORM: Introduce async platform_data attach
 api

On 03/13/2011 04:15 PM, Somebody in the thread at some point said:
> On Sun, Mar 13, 2011 at 01:21:20PM +0000, Andy Green wrote:
>> On 03/13/2011 12:53 PM, Somebody in the thread at some point said:
>>
>>>>>> This _really_ should just use the device tree stuff, that is what it is
>>>>>> for, please don't duplicate it here in a not-as-flexible way.
>>>>>
>>>>> I agree.
>>>>>
>>>>> @Andy: If it doesn't work for you for some reason, please let us know the
>>>>> usage case that is not covered (in detail).
>>>>
>>>> The device tree stuff does not yet exist in a workable way,
>>>> platform_data is established everywhere except USB bus.  Device tree
>>>> brings in bootloader version as a dependency: this method doesn't.
>>>
>>> It is not the same device tree we are talking about. :-)
>>>
>>> I mean device hierarchy (and I guess Greg meant the same).
>>
>> I see.  Elsewhere on the previous thread people were proposing to
>> use New Shiny Device Tree, hence the confusion.
>
> Yes, I meant the "new shiny device tree" work from Grant, who in an
> earlier message, said that this could all be done using that instead of
> your proposal.

That is what I took you to mean, since I already use oldstyle device 
tree as far as I could see it was possible.  So I have no idea what 
Rafael thought you or he meant by strongly agreeing with you when he was 
mistaken that thought you meant oldstyle device tree.  Anyway never mind.

Well I never heard mentioned before that Device Tree targets 
asynchronously probed device configuration.  If it does, and can do the 
same effective as the first patchset, then I guess that will (when it 
exists) fulfil a similar job and that'd be fine.

But what this overall patch set does in panda.c, usbnet and smsc95xx 
will need the same work done on it either way to deliver the same new 
configuration features in the driver side, via Shiny New Device Tree or 
whatever.

So when there's a bit more of Device Tree in evidence, are you going to 
accept Device-tree based patches in usbnet etc along these lines, or 
does that trigger the "do it in userspace" response, in which case we 
are both wasting each others' time continuing to discuss this at all?

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