linux-kernel - Re: [sodaville] [PATCH TIP 02/14] x86: Add device tree 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: <20110217113102.GB11260@www.tglx.de>
Date:	Thu, 17 Feb 2011 12:31:02 +0100
From:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:	Grant Likely <grant.likely@...retlab.ca>
Cc:	Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
	sodaville@...utronix.de, devicetree-discuss@...ts.ozlabs.org,
	x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [sodaville] [PATCH TIP 02/14] x86: Add device tree support

* Grant Likely | 2011-02-16 14:31:26 [-0700]:

>> +config X86_OF
>> +	bool "Support for device tree"
>> +	select OF
>> +	select OF_EARLY_FLATTREE
>> +	---help---
>> +	  Device tree support on X86.
>> +
>
>On ARM and MIPS, this is called 'config USE_OF'.  It would be nice to have
>some commonality.  Maybe I should move the user-visible option to
>drivers/of/Kconfig.  Or perhaps I should just make CONFIG_OF itself
>user visible.
>
>thoughts?

We could make CONFIG_OF depend on CONFIG_HAVE_OF_SUPPORT and let OF
select OF_EARLY_FLATTREE if ARCH_WANT_EARLY_FLATTREE for instance. So
that part would work in a generic way.

For OF-only platforms you would have to go to drivers/of
before you can enable the specific SoC/board. So it could lead to
something like "first enable scsi disk before you can enable usb
storage".

I like it :) For now I rename to USE_OF.

>
>g.

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