public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Andres Salomon <dilinger@queued.net>,
	devicetree-discuss@lists.ozlabs.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: OLPC: add OLPC device-tree support (v3)
Date: Wed, 27 Oct 2010 07:41:20 -0700	[thread overview]
Message-ID: <4CC83A10.8090607@zytor.com> (raw)
In-Reply-To: <20101027101933.GD6797@angua.secretlab.ca>

On 10/27/2010 03:19 AM, Grant Likely wrote:
> On Fri, Oct 22, 2010 at 03:58:46PM -0700, Andres Salomon wrote:
>>
>> Make use of PROC_DEVICETREE to export the tree, and sparc's PROMTREE code to
>> call into OLPC's Open Firmware to build the tree.
>>
>> v3: rename olpc_prom to olpc_dt
>>   - rework Kconfig entries
>>   - drop devtree build hook from proc, instead adding a call to x86's
>>     paging_init (similarly to how sparc64 does it)
>>   - switch allocation from using slab to alloc_bootmem.  this allows
>>     the DT to be built earlier during boot (during setup_arch); the
>>     downside is that there are some 1200 bootmem reservations that are
>>     done during boot.  Not ideal..
>>   - add a helper olpc_ofw_is_installed function to test for the
>>     existence and successful detection of OLPC's OFW.
>>
>> Signed-off-by: Andres Salomon <dilinger@queued.net>
> 
> Overall this patch looks fine, but it needs to be acked from the x86
> maintainers, and I'd like it to have a cycle through linux-next before
> it gets merged, so that means 2.6.38 because the 2.6.37 merge window
> has already been open for almost a week.
> 

Right... which means that our attention is going to be elsewhere for a
bit -- probably until after KS/LPC.  Sorry, just immediate
prioritization and nothing to do with the relative importance.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  parent reply	other threads:[~2010-10-27 14:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 22:58 [PATCH] x86: OLPC: add OLPC device-tree support (v3) Andres Salomon
2010-10-23  0:22 ` [PATCH] x86: OLPC: speed up device tree creation during boot Andres Salomon
2010-10-27 10:39   ` Grant Likely
2010-10-27 17:50     ` Andres Salomon
2010-10-27 10:19 ` [PATCH] x86: OLPC: add OLPC device-tree support (v3) Grant Likely
2010-10-27 13:35   ` Thomas Gleixner
2010-10-27 14:41   ` H. Peter Anvin [this message]
2010-10-27 17:48   ` Andres Salomon

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=4CC83A10.8090607@zytor.com \
    --to=hpa@zytor.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dilinger@queued.net \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    /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