mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] defaultenv: make 'boot' work from subdirs
Date: Mon, 10 Jan 2011 20:50:34 +0100	[thread overview]
Message-ID: <20110110195034.GJ24920@pengutronix.de> (raw)
In-Reply-To: <1294658358-18311-1-git-send-email-w.sang@pengutronix.de>

Hi Wolfram,

On Mon, Jan 10, 2011 at 12:19:18PM +0100, Wolfram Sang wrote:
> Wrong pathnames prevented that.
> 
> Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
> ---
>  defaultenv/bin/boot |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/defaultenv/bin/boot b/defaultenv/bin/boot
> index 42c7ec2..4c2975d 100644
> --- a/defaultenv/bin/boot
> +++ b/defaultenv/bin/boot
> @@ -56,13 +56,13 @@ fi
>  
>  if [ ! -e /dev/ram0.kernelraw ]; then
>  	# arm raw kernel images are usually located at sdram start + 0x8000
> -	addpart dev/ram0 8M@0x8000(kernelraw)
> +	addpart /dev/ram0 8M@0x8000(kernelraw)
>  fi
>  
>  if [ ! -e /dev/ram0.kernel ]; then
>  	# Here we can safely put the kernel without risking of overwriting it
>  	# while extracting
> -	addpart dev/ram0 8M@8M(kernel)
> +	addpart /dev/ram0 8M@8M(kernel)
>  fi
I stumbled over this one some time ago, too.  but never came around to
look for its cause.  Thanks, looks good.

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

      reply	other threads:[~2011-01-10 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 11:19 Wolfram Sang
2011-01-10 19:50 ` Uwe Kleine-König [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=20110110195034.GJ24920@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=w.sang@pengutronix.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