All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Status of u-boot-fdt
Date: Tue, 07 Aug 2007 21:56:41 -0400	[thread overview]
Message-ID: <46B922D9.2070909@gmail.com> (raw)

Hi All,

I've updated my simple message improvement patch per Kim's suggestion 
and reposted.  I've rebased against The Master (u-boot, not Wolfgang ;-).

I believe the u-boot-fdt repo is ready to be pulled and will call for 
Wolfgang to pull it, probably tomorrow morning.  Holler now or squeal 
after the fact.

Missing patches:
* Andy Fleming's patch WRT making sure the blob is in the lower portion
    (16GB at the moment) of memory.  Still being discussed.

* Unpublished patch of mine, implementing a suggestion by Scott Wood to
    make the /chosen handling finer grained: if the /chosen node exists,
    currently u-boot-fdt bails out.  A better methodology is to not
    overwrite pre-existing properties on a per-property basis, so if
    /chosen exists but a necessary /chosen/property doesn't, it gets
    created.  Good idea, but not published and poorly tested at the
    moment.

Best regards,
gvb

                 reply	other threads:[~2007-08-08  1:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=46B922D9.2070909@gmail.com \
    --to=gvb.uboot@gmail.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.