LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Amit Kucheria <amit.kucheria@linaro.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: devicetree-discuss <devicetree-discuss@lists.ozlabs.org>,
	linaro-dev <linaro-dev@lists.linaro.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Device Tree on ARM status report
Date: Mon, 7 Feb 2011 10:46:13 +0200	[thread overview]
Message-ID: <20110207084613.GC2723@matterhorn.lan> (raw)
In-Reply-To: <AANLkTikLvO0Y44nCxEfCsNxU-Na+PzcLXZUjOsMUM1_A@mail.gmail.com>

On 11 Feb 05, Grant Likely wrote:
> Hi all,
> 
> With several more engineers working on ARM device tree support, I'm
> going to start collecting the status of all the work that is going on
> (and I know about) and posting it in a regular status report,
> hopefully weekly, for the next few months until the all of the major
> features are implemented and working on several arm platforms.  I'll
> try to use roughly the following format:
> 
> 1) latest news and status updates
> 2) list of tasks with current state and who is responsible for them in
> the same format as Launchpad blueprint whiteboards[1]. (In fact, I'll
> probably move much, if not all, of this into Launchpad anyway, in
> which case these emails will be a summary of all the blueprints. not
> all of us work with Linaro, but it is a useful method for tracking
> progress).
> 3) List of active engineers
> 
> [1] https://wiki.linaro.org/Process/Blueprints
> 
> Please read through and reply with comments/corrections.  Feel free to
> add or remove tasks from the list I've given below.
> 
> Thanks,
> g.
> 
> 
> 1 - Latest news
> ---------------
> - devicetree/arm on git://git.secretlab.ca/git/linux-2.6 has
> everything needed to turn on basic device tree support for any
> platform.
> - Similarly, u-boot just needs to have the CONFIG_OF_LIBFDT defined to
> turn on device tree support.
> - IRQ handling is still a problem and only one interrupt controller
> can be supported at the moment, but Lennert is working on a solution.
> - I've posted a patch that will allow dt and non-dt device
> registration to co-exist peacefully by snooping platform device
> registrations.  I could use some feedback and testing.
> - hopefully the basic dt support can be merged into Nicolas' tree this
> week if I get a cleaned up branch pushed out for him quickly.
> 
> 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.

Regards,
Amit

  parent reply	other threads:[~2011-02-07  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06  4:42 Grant Likely
2011-02-06 13:36 ` Thomas Abraham
2011-02-07  8:46 ` Amit Kucheria [this message]
2011-02-07 21:28   ` Grant Likely
2011-02-08 11:51     ` Lorenzo Pieralisi
2011-02-07 11:49 ` Shawn Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110207084613.GC2723@matterhorn.lan \
    --to=amit.kucheria@linaro.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: Device Tree on ARM status report' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).