Devicetree
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
Cc: devicetree-discuss
	<devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org>
Subject: Re: The new DTS language enhancements
Date: Wed, 1 Oct 2008 16:51:09 -0600	[thread overview]
Message-ID: <fa686aa40810011551w7250a5cdoc0d928456ea34d3b@mail.gmail.com> (raw)
In-Reply-To: <3643ED8C-2AED-405A-8C7E-432FB311DE6A-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>

On Wed, Oct 1, 2008 at 3:11 PM, Kumar Gala <galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org> wrote:
>
> On Oct 1, 2008, at 2:37 PM, Jon Loeliger wrote:
>
>> Folks,
>>
>> We have had some internal discussion inside Freescale
>> about my proposed DTS language enhancements now.
>> We feel that we have significant need for this approach,
>> and in the absence of a solid alternate proposal,
>> we would like to move forward with it.
>
> I agree with Jon here... if people aren't going to have useful comments on
> what changes need to be made to Jon's work we'd (Freescale) like to see a
> dtc-2.0 with these changes and getting those changes into the kernel for
> 2.6.28.

Jon's changes are non-trivial and have long lasting implications.
First posting of the changes was made on Sept 23, just over a week
ago.  Jon told me about the new design only a month ago.  Not a lot of
time.

This is not the same as adding a new driver or supporting a new SoC.
The consequences have considerable broader reach.  Time must be
allowed for us to mull over the design.

Merging for 2.6.28 is too aggressive.

I appreciate that you're frustrated with the lack of alternate
proposals, but there hasn't been enough time yet.

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-10-01 22:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 19:37 The new DTS language enhancements Jon Loeliger
2008-10-01 21:11 ` Kumar Gala
     [not found]   ` <3643ED8C-2AED-405A-8C7E-432FB311DE6A-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2008-10-01 22:51     ` Grant Likely [this message]
     [not found]       ` <fa686aa40810011551w7250a5cdoc0d928456ea34d3b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-02  0:42         ` David Gibson
     [not found]           ` <20081002004247.GD25598-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-10-02  3:38             ` Kumar Gala
2008-10-02  3:45         ` Kumar Gala
     [not found]           ` <11973616-0AA9-4CA4-BC12-7B896DDF533C-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2008-10-02 11:50             ` Josh Boyer
     [not found]               ` <20081002075053.400e4adf-jnIq6iUNB1CO8iYQgJmm/0EOCMrvLtNR@public.gmane.org>
2008-10-02 12:49                 ` Kumar Gala
2008-10-02 14:36             ` David Gibson
     [not found]               ` <20081002143648.GJ11662-787xzQ0H9iRg7VrjXcPTGA@public.gmane.org>
2008-10-02 16:23                 ` Jon Loeliger
2008-10-03  1:02                   ` David Gibson

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=fa686aa40810011551w7250a5cdoc0d928456ea34d3b@mail.gmail.com \
    --to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
    --cc=devicetree-discuss-mnsaURCQ41sdnm+yROfE0A@public.gmane.org \
    --cc=galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox