devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
To: For discussion of Syslinux and tftp-hpa
	<syslinux-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [syslinux] [RFC 0/2] syslinux: Add device tree support
Date: Fri, 29 Jun 2012 15:37:54 -0700	[thread overview]
Message-ID: <4FEE2E42.2000707@zytor.com> (raw)
In-Reply-To: <1338478896-11417-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>

On 05/31/2012 08:41 AM, Thierry Reding wrote:
> This patch series adds support for passing a Flattened Device Tree (FDT)
> blob to the Linux kernel. Currently, only the linux.c32 module can do so
> and some additional checking should be done to only pass the blob if the
> kernel supports boot protocol 2.09 or later.
> 
> Thierry

Hi there,

I just merged a modified/more generic version of your patch.  I would
appreciate it if you could test it and report back.

	-hpa

  parent reply	other threads:[~2012-06-29 22:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 15:41 [RFC 0/2] syslinux: Add device tree support Thierry Reding
     [not found] ` <1338478896-11417-1-git-send-email-thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>
2012-05-31 15:41   ` [RFC 1/2] com32: " Thierry Reding
2012-05-31 15:41   ` [RFC 2/2] linux.c32: Add initrd= parameter Thierry Reding
2012-06-29 22:37   ` H. Peter Anvin [this message]
     [not found]     ` <4FEE2E42.2000707-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>
2012-07-02  6:49       ` [syslinux] [RFC 0/2] syslinux: Add device tree support Thierry Reding
     [not found]         ` <20120702064907.GB8683-RM9K5IK7kjIQXX3q8xo1gnVAuStQJXxyR5q1nwbD4aMs9pC9oP6+/A@public.gmane.org>
2012-07-02 13:05           ` H. Peter Anvin

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=4FEE2E42.2000707@zytor.com \
    --to=hpa-ymnouzjc4hwavxtiumwx3w@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=syslinux-YMNOUZJC4hwAvxtiuMwx3w@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;
as well as URLs for NNTP newsgroup(s).