Hi Sanjeev,
Is there any update on the fix/proposal?
I am trying to build for omap3_evm; but see the same problem.
My repo is currently at:
bb3bcfa : Merge branch 'next' of ../next
a200a7c : Update CHANGELOG; prepare Prepare v2009.11
As Scott pointed out rightly, my previous
Hi Scott,
Hunk 1:
env_addr = CONFIG_ENV_ADDR;
+ if (FLEXONENAND(this))
+ env_addr = 1;
Hunk 2:
+ if (FLEXONENAND(this)) {
+ env_addr = 1;
+ instr.len =
onenand_mtd.eraseregions[0].numblocks == 1 ?
+
Hi Scott,
Are they going to be the same on all boards? We let the
board determine the environment location for other types of storage.
OK
How about just using CONFIG_ENV_ADDR/CONFIG_ENV_SIZE? On
boards that must dynamically support multiple possibilities,
define it as an expression
Hi,
-Original Message-
From: rub...@gnudd.com [mailto:rub...@gnudd.com] On Behalf Of
Alessandro Rubini
Sent: Tuesday, December 01, 2009 9:36 PM
To: tom@windriver.com
Cc: moorthy@samsung.com; scottw...@freescale.com;
u-boot@lists.denx.de; kyungmin.p...@samsung.com
Hi Tom,
Amul is out-of-office for sometime.
Excuse us for the delay.
In rebasing arm/next against u-boot/next.
There is a general error with targets that use onenand.
This includes the targets
nk8815_onenand
omap3_evm
smdkc100
I believe the error is from
commit
Hi,
With OneNAND ipl reading CONFIG_SYS_MONITOR_LEN , Environment Area
should start after CONFIG_SYS_MONITOR_LEN.
Environment is made Bad Block cpapable too. These are done in the patch.
And fix 'onenand test' command to skip Bootloader and Environment Blocks.
With Regards
Moorthy
Hi Scott,
On Tuesday, March 31, 2009 4:04 AM Scott Wood Wrote :
Note that there are a couple of board files (apollon and nmdk8815) that use
the OneNAND loader
that do not define CONFIG_SYS_MONITOR_LEN. I've added the maintainers to the
Cc: list.
CONFIG_SYS_MONITOR_LEN is not defined in
On Apr 05, 2009 01:40 Jean-Christophe Wrote :
Your patch Fix OneNAND ipl to read CONFIG_SYS_MONITOR_LEN
brake the appolon
Could you take a look?
- Can you please do let me know , where exactly do you see a problem ?
With Regards
Moorthy
Currently OneNAND initial program loader (ipl) reads only block 0 ie 128KB.
However, u-boot image for apollon board is 195KB making the board
unbootable with OneNAND.
Fix ipl to read CONFIG_SYS_MONITOR_LEN.
CONFIG_SYS_MONITOR_LEN macro holds the U-Boot image size.
Signed-off-by: Rohit
Hi Scott,
On Tuesday, March 24, 2009 2:55 AM , Scott Wood wrote
Please do find the updated patch below.
It's easier if updated patches are sent separately from the reply (both to
avoid getting lost,
and to avoid having to manually strip discussion from the changelog).
Signed-off-by:
Hi Scott,
+if (page 2 (onenand_readw(THIS_ONENAND(ONENAND_SPARERAM)) !=
0x))
Line length.
- Corrected.
int pagesize = ONENAND_PAGE_SIZE;
+int nblocks = CONFIG_SYS_MONITOR_LEN / ONENAND_BLOCK_SIZE;
Shouldn't nblocks be rounded up?
pagesize =
Hi All,
This patch adds support for Samsung Flex-OneNAND devices.
Flex-OneNAND combines SLC and MLC technologies into a single
device. SLC area provides increased reliability and speed, suitable
for storing code and data, such as bootloader, kernel
and root file system. MLC area provides high
12 matches
Mail list logo
