public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Fix OneNAND ipl to read 256KB
Date: Thu, 26 Feb 2009 13:47:03 +0100	[thread overview]
Message-ID: <20090226124703.GA10994@game.jcrosoft.org> (raw)
In-Reply-To: <49A68BA2.80807@samsung.com>

On 18:01 Thu 26 Feb     , Rohit Hagargundgi wrote:
> Hi,
>
> Jean-Christophe PLAGNIOL-VILLARD wrote:
>>>   #define ONENAND_BLOCK_SIZE              2048
>>> +#define ONENAND_BOOTLOADER_SIZE		0x40000
>> why hardcoded value?
>
> Is it possible to get image size instead of hard value.
> Then we can read exactly u-boot image size on boot up.
as point out Wolfgang you can use the MONITOR_LEN.

If you really need the u-boot.bin size you will need to built it first and then
on the host calculate it and genereate a .h with its size.

But IMHO the MONITOR_LEN will give enough information evenif it's not the real size
to copy u-boot in memory

Best Regards,
J.

  reply	other threads:[~2009-02-26 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-26  7:33 [U-Boot] [PATCH] Fix OneNAND ipl to read 256KB Rohit Hagargundgi
2009-02-26  8:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-02-26 12:31   ` Rohit Hagargundgi
2009-02-26 12:47     ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2009-02-26 13:56     ` Wolfgang Denk
2009-02-26  8:23 ` Wolfgang Denk
2009-02-26 10:34   ` Kyungmin Park
2009-02-26 20:01     ` Rohit Hagargundgi
2009-03-04 15:09       ` Rohit Hagargundgi
2009-03-04 23:55         ` Kyungmin Park
2009-03-08  6:50           ` Rohit Hagargundgi
2009-03-08 22:44         ` Wolfgang Denk
2009-03-09 10:34           ` Rohit Hagargundgi
2009-03-09 11:55             ` Wolfgang Denk

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=20090226124703.GA10994@game.jcrosoft.org \
    --to=plagnioj@jcrosoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox