mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Vicente Bergas <vicencb@gmail.com>
To: barebox@lists.infradead.org
Cc: Vicente Bergas <vicencb@gmail.com>
Subject: [PATCH 0/2] DeviceTree: add support for initrd in the DT
Date: Sun, 10 Feb 2013 17:58:55 +0100	[thread overview]
Message-ID: <1360515537-1703-1-git-send-email-vicencb@gmail.com> (raw)

Following Jean-Christophe's recommendation the patch has been splitted in two,
supressed extra spaces and substituted a ==NULL for a !.

Regarding to the questions:
I'm not checking the return value of fdt_initrd because in case of error
 1) fdt_initrd will print a message to inform the user.
 2) it's not a blocking error (from the bootloader point-of-view), so we can still try to boot.
fdt_setprop gets a buffer of data that must be in BigEndian order to be standard compliant.
 It's defined to be BigEndian probably because it comes from PowerPC.
 I've also tested it before submitting and it works fine.

Thank you for your comments.
Regards,
  Vicente.

Vicente Bergas (2):
  DeviceTree: add support for initrd in the DT
  ArchosG9: boot linux kernel with DT

 arch/arm/boards/archosg9/env/config       |  1 +
 arch/arm/configs/archosg9_defconfig       |  4 ++
 arch/arm/configs/archosg9_xload_defconfig |  1 +
 arch/arm/lib/armlinux.c                   |  2 +
 common/oftree.c                           | 66 +++++++++++++++++++++++++++++++
 include/of.h                              |  1 +
 6 files changed, 75 insertions(+)

-- 
1.8.1.3


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2013-02-10 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 16:58 Vicente Bergas [this message]
2013-02-10 16:58 ` [PATCH 1/2] " Vicente Bergas
2013-02-11  9:55   ` Sascha Hauer
2013-02-10 16:58 ` [PATCH 2/2] ArchosG9: boot linux kernel with DT Vicente Bergas

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=1360515537-1703-1-git-send-email-vicencb@gmail.com \
    --to=vicencb@gmail.com \
    --cc=barebox@lists.infradead.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