linux-kernel - Re: Device Tree on ARM status report

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: <AANLkTi=dK2qYTH7vThJb8-3wED5F_5Hcmr7nNidxs25c@mail.gmail.com>
Date:	Mon, 7 Feb 2011 14:28:47 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Grant Likely <grant.likely@...retlab.ca>,
	devicetree-discuss <devicetree-discuss@...ts.ozlabs.org>,
	linaro-dev <linaro-dev@...ts.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Device Tree on ARM status report

On Mon, Feb 7, 2011 at 1:46 AM, Amit Kucheria <amit.kucheria@...aro.org> wrote:
> On 11 Feb 05, Grant Likely wrote:
>> 2 - Task status
>> ---------------
>> Core infrastructure:
>> [glikely] basic infrastructure to enable dt: DONE
>> [r-herring] Allow dtb to be located anywhere in RAM: DONE
>> [bones] Debug dtb corruption during init: INPROGRESS
>> [glikely] OF clock bindings: INPROGRESS
>
> Does this include the common clock framework that Jeremy had been working on?
> I see no mention of that explicitly, hence the question.

No, since the common clk patches are taking some time to get right,
the device tree clock bindings have been decoupled from the common clk
patches so that dt support doesn't get held up.  When common clk gets
merged, the dt support will be modified to use it.

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