mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Xavier Douville <barebox@douville.org>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/1] commands/ubi.c: Add support for VID header offset in ubiattach
Date: Mon, 11 Feb 2013 10:14:50 -0500	[thread overview]
Message-ID: <20130211151452.DHP25653.toroondcbmts04-srv.bellnexxia.net@toip41-bus.srvr.bell.ca> (raw)
In-Reply-To: <20130211091905.GQ1906@pengutronix.de>

Hi

Sascha Hauer wrote:
> I don't know exactly, but I suspect something is wrong on your board then. Normally the VID header offset should be detected correctly automatically. Does the kernel also need a special VID header offset? Have you flashed an UBI image or did you generate the UBI on the target directly? 

I also need to specify VID header offset 2048 to the kernel. It came configured as such from the vendor (phytec, board am335x).
I flashed an UBI image generated by ptxdist.

If the kernel has this option, shouldn't barebox have it too?

If you are still interested by the patch, I will format it properly, using getopt() and without line wraps.

thanks

Xavier Douville

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

  reply	other threads:[~2013-02-11 15:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 20:01 Xavier Douville
2013-02-11  9:19 ` Sascha Hauer
2013-02-11 15:14   ` Xavier Douville [this message]
2013-02-11 15:21     ` Sascha Hauer
2013-02-14 16:23       ` Jan Lübbe
2013-02-15 15:54         ` Xavier Douville
2013-02-15 16:06           ` Jan Lübbe
2013-02-15 16:58             ` Xavier Douville
2013-02-12 22:49     ` Marc Kleine-Budde
2013-02-12 22:52       ` Jean-Christophe PLAGNIOL-VILLARD
2013-02-13  9:00         ` Marc Kleine-Budde
2013-02-12 15:31   ` [PATCH] Do not print error message when successfully attaching more than one UBI device Xavier Douville

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=20130211151452.DHP25653.toroondcbmts04-srv.bellnexxia.net@toip41-bus.srvr.bell.ca \
    --to=barebox@douville.org \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@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