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] [PATCH v3] Add sub-commands to fdt
Date: Sat, 16 Feb 2008 17:28:47 -0500	[thread overview]
Message-ID: <47B7639F.6070601@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0802151557050.16787@blarg.am.freescale.net>

Kumar Gala wrote:
>>From e76f97d16c5932d19d698e42c6376d6bbdca2ecf Mon Sep 17 00:00:00 2001
> From: Kumar Gala <galak@kernel.crashing.org>
> Date: Fri, 15 Feb 2008 03:34:36 -0600
> Subject: [PATCH] Add sub-commands to fdt
> 
> fdt header                          - Display header info
> fdt bootcpu <id>                    - Set boot cpuid
> fdt memory <addr> <size>            - Add/Update memory node
> fdt rsvmem print                    - Show current mem reserves
> fdt rsvmem add <addr> <size>        - Add a mem reserve
> fdt rsvmem delete <index>           - Delete a mem reserves
> 
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>

Applied to u-boot-fdt.  Thanks.

FWIIW, I found that fdt header when the fdt address (blob) is invalid 
crashes my board.  On the one hand, that's what you get from playing 
with sharp knives - I'm reluctant to inhibit the header printout if the 
blob is invalid, because that may be what I'm trying to find out.  On 
the other hand, I hate to crash a board when it can be avoided.

At this point, I'm inclined to validate the magic number (only) before 
doing the dump.

gvb

      reply	other threads:[~2008-02-16 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15  9:36 [U-Boot-Users] [PATCH] Add sub-commands to fdt Kumar Gala
2008-02-15 14:09 ` Jerry Van Baren
2008-02-15 14:38   ` Kumar Gala
2008-02-15 14:39   ` [U-Boot-Users] [PATCH v2] " Kumar Gala
2008-02-15 21:44 ` [U-Boot-Users] [PATCH] " Jerry Van Baren
2008-02-15 21:51   ` Kumar Gala
2008-02-15 21:57     ` [U-Boot-Users] [PATCH v3] " Kumar Gala
2008-02-16 22:28       ` Jerry Van Baren [this message]

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=47B7639F.6070601@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.