netdev - Re: [PATCH v2 0/2] net: thunder: Add ACPI support.

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]

Message-Id: <20150811.135019.576312282566025940.davem@davemloft.net>
Date:	Tue, 11 Aug 2015 13:50:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	robert.richter@...iumnetworks.com
Cc:	ddaney@...iumnetworks.com, ddaney.cavm@...il.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-mips@...ux-mips.org, tomasz.nowicki@...aro.org,
	sgoutham@...ium.com, linux-arm-kernel@...ts.infradead.org,
	linux-acpi@...r.kernel.org, mark.rutland@....com,
	rafael@...nel.org, david.daney@...ium.com
Subject: Re: [PATCH v2 0/2] net: thunder: Add ACPI support.

From: Robert Richter <robert.richter@...iumnetworks.com>
Date: Tue, 11 Aug 2015 22:12:37 +0200

> On 11.08.15 13:04:55, David Daney wrote:
>> >In the future it might be better structured to try and get the OF
>> >node, and if that fails then try and use the ACPI method to obtain
>> >these values.
>> 
>> Our current approach, as you can see in the patch, is the opposite.  If ACPI
>> is being used, prefer that over the OF device tree.
>> 
>> You seem to be recommending precedence for OF.  It should be consistent
>> across all drivers/sub-systems, so do you really think that OF before ACPI
>> is the way to go?
> 
> If ACPI is enabled then no OF function may be called at all.

That makes no sense to me at all.

If ACPI is enabled, the OF routines should return no nodes etc.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html