mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Victor Rodriguez <vm.rod25@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: Beagleboard and barebox problem
Date: Tue, 26 Oct 2010 20:34:49 +0200	[thread overview]
Message-ID: <20101026183449.GE6017@pengutronix.de> (raw)
In-Reply-To: <AANLkTi==hZCG9TbR1udevZPJp=wbji-JTTZaMTYYcW6f@mail.gmail.com>

On Mon, Oct 25, 2010 at 11:07:21PM -0500, Victor Rodriguez wrote:
> On Mon, Oct 25, 2010 at 10:39 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > Hi Victor,
> >
> > Right, dont forget to erase the partitions with 'erase
> > /dev/nand0.kernel.bb' beforehand, otherwise you'll have garbage in your
> > nand.
> 
> You mean to erase the part of the nand where the kernel is saved
> before copy the ramdisk to its partition? or before i run the 'boot'
> comand ?

You have to erase the Nand before writing to it. (though I wonder if
that behaviour should be changed).

> >
> > I'm sorry the situation on the beagle board is still a bit rough and
> > unclear. I hope we find time working on this.
> 
> 
> Yes I could give some free time to work on this :) but could you
> please give me more information about the mmc dirver I am new on
> barebox but I would like to help to improve it  :)

Great ;)

> 
> Which other board is using this MMC driver ? I can check the code.

Currently there is no Omap MMC support in barebox. The path to go would
be to copy the Omap MMC driver from U-Boot and bash onto it until it
runs. For a clue what has to be changed in this driver you might want to
look at a diff between the i.MX esdhc driver inU-Boot and barebox.

> 
> The problem is that beagle board is much more familiar with booting by
> mmc because it does not have any RJ45 connector in order to transfer
> by TFTP or NFS the uImage.
> 
> By the way about the small piece of code for the beagle board nand. Do
> you consider that is good enough for an small patch ?

I think at least the offset of the environment has to be moved. AFAIK
the first 768k in Nand is used for the Xloader and the secoond stage
bootloader. It's probably not good for users overwriting this
accidently.

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

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

      reply	other threads:[~2010-10-26 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 17:55 Victor Rodriguez
2010-10-22  7:05 ` Sascha Hauer
2010-10-25 22:29   ` Victor Rodriguez
2010-10-26  3:39     ` Sascha Hauer
2010-10-26  4:07       ` Victor Rodriguez
2010-10-26 18:34         ` Sascha Hauer [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=20101026183449.GE6017@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=vm.rod25@gmail.com \
    /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