Re: [U-Boot] [PATCH 1/1 V3] Add support for LZMA uncompression algorithm.
HI Wolfgang, the lzma.txt file is from the original sources. thanks for applying this patch. luigi 2008/9/13 Wolfgang Denk <[EMAIL PROTECTED]>: > Dear Jean-Christophe PLAGNIOL-VILLARD, > > In message <[EMAIL PROTECTED]> you wrote: >> --===0188417863== >> >> From: Luigi 'Comio' Mantellini <[EMAIL PROTECTED]> >> >> Signed-off-by: Luigi 'Comio' Mantellini <[EMAIL PROTECTED]> >> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[EMAIL PROTECTED]> >> --- >> Add missing lzma/Makefile >> Makefile |1 + >> README | 23 ++ >> common/cmd_bootm.c | 23 ++ >> common/image.c |1 + >> include/image.h|1 + >> include/lzma/LzmaDecode.h | 31 ++ >> include/lzma/LzmaTools.h | 31 ++ >> include/lzma/LzmaTypes.h | 31 ++ >> lib_generic/lzma/LGPL.txt | 504 +++ >> lib_generic/lzma/LzmaDecode.c | 584 +++ >> lib_generic/lzma/LzmaDecode.h | 113 ++ >> lib_generic/lzma/LzmaTools.c | 142 >> lib_generic/lzma/LzmaTools.h | 35 ++ >> lib_generic/lzma/LzmaTypes.h | 45 +++ >> lib_generic/lzma/Makefile | 50 +++ >> lib_generic/lzma/README.txt| 28 ++ >> lib_generic/lzma/history.txt | 198 +++ >> lib_generic/lzma/import_lzmasdk.sh | 38 ++ >> lib_generic/lzma/lzma.txt | 663 >> >> 19 files changed, 2542 insertions(+), 0 deletions(-) >> create mode 100644 include/lzma/LzmaDecode.h >> create mode 100644 include/lzma/LzmaTools.h >> create mode 100644 include/lzma/LzmaTypes.h >> create mode 100644 lib_generic/lzma/LGPL.txt >> create mode 100644 lib_generic/lzma/LzmaDecode.c >> create mode 100644 lib_generic/lzma/LzmaDecode.h >> create mode 100644 lib_generic/lzma/LzmaTools.c >> create mode 100644 lib_generic/lzma/LzmaTools.h >> create mode 100644 lib_generic/lzma/LzmaTypes.h >> create mode 100644 lib_generic/lzma/Makefile >> create mode 100644 lib_generic/lzma/README.txt >> create mode 100644 lib_generic/lzma/history.txt >> create mode 100644 lib_generic/lzma/import_lzmasdk.sh >> create mode 100644 lib_generic/lzma/lzma.txt > > Applied, but please be abit more careful about Coding style > requirements: > > Applying Add support for LZMA uncompression algorithm. > .dotest/patch:414: trailing whitespace. > > .dotest/patch:779: trailing whitespace. > > .dotest/patch:786: trailing whitespace. > It means that you can select one of these two licenses and > .dotest/patch:790: trailing whitespace. > Igor Pavlov, as the author of this Code, expressly permits you to > .dotest/patch:791: trailing whitespace. > statically or dynamically link your Code (or bind by name) to the > warning: squelched 171 whitespace errors > warning: 176 lines applied after fixing whitespace errors. > > > Best regards, > > Wolfgang Denk > > -- > DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany > Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] > Space is big. You just won't believe how vastly, hugely, mind- > bogglingly big it is. I mean, you may think it's a long way down the > road to the drug store, but that's just peanuts to space. > -- The Hitchhiker's Guide to the Galaxy > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > -- Luigi 'Comio' Mantellini R&D - Software Industrie Dial Face S.p.A. Via Canzo, 4 20068 Peschiera Borromeo (MI), Italy Tel.: +39 02 5167 2813 Fax: +39 02 5167 2459 web: www.idf-hit.com mail: [EMAIL PROTECTED] ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] Update mailing list email and archive addresses
Dear Peter Tyser, In message <[EMAIL PROTECTED]> you wrote: > Signed-off-by: Peter Tyser <[EMAIL PROTECTED]> > --- > > The reference to [EMAIL PROTECTED] on this page should also be > updated: http://www.denx.de/wiki/U-Boot/Patches > > MAINTAINERS |2 +- > README |8 > 2 files changed, 5 insertions(+), 5 deletions(-) Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] If a train station is a place where a train stops, then what's a workstation? ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] mpc85xx/31
Synopsis: [PATCH] 85xx: socrates: autoprobe Lime chip State-Changed-From-To: open->closed State-Changed-By: wd State-Changed-When: Sat, 13 Sep 2008 02:10:19 +0200 State-Changed-Why: Applied as commit fb661ea444ae61de60520f66ae84cdb5dd5a3246 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] mpc85xx/30
Synopsis: [PATCH] 85xx: socrates: Add support for new image format. State-Changed-From-To: open->closed State-Changed-By: wd State-Changed-When: Sat, 13 Sep 2008 02:09:41 +0200 State-Changed-Why: Applied as commit e99b607a5ec56ce66e0bcccb78480d5e16fb7bc5 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] unassigned-patches/31: [PATCH] 85xx: socrates: autoprobe Lime chip
Dear Anatolij, In message <[EMAIL PROTECTED]> you wrote: > This patch is an attempt to implement autoprobing for the Lime > presence on the bus. > Configure GPCM for Lime CS2 and try to access chip ID registers. > Second read atempt delivers register values if the chip is present. > > Signed-off-by: Anatolij Gustschin <[EMAIL PROTECTED]> > > --- > board/socrates/socrates.c | 58 +--- > 1 files changed, 43 insertions(+), 15 deletions(-) Applied, thanks. Andy, I hope / guess this is OK with you. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Leave bigotry in your quarters; there's no room for it on the bridge. -- Kirk, "Balance of Terror", stardate 1709.2 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] unassigned-patches/30: [PATCH] 85xx: socrates: Add support for new image format.
Dear Detlev, In message <[EMAIL PROTECTED]> you wrote: > Signed-off-by: Detlev Zundel <[EMAIL PROTECTED]> > > include/configs/socrates.h |5 + > 1 files changed, 5 insertions(+), 0 deletions(-) Applied, thanks. Andy, I hope / guess this is OK with you. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Of all the things I've lost, I miss my mind the most. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH] sh: Fix compile error for r2dplus
Dear Nobuhiro Iwamatsu, In message <[EMAIL PROTECTED]> you wrote: > netdev.h was not include by r2dplus. > > Signed-off-by: Nobuhiro Iwamatsu <[EMAIL PROTECTED]> > --- > board/r2dplus/r2dplus.c |1 + > 1 files changed, 1 insertions(+), 0 deletions(-) Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Copy from one, it's plagiarism; copy from two, it's research. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v3] powerpc: Fix bootm to boot up again with a Ramdisk
Dear Heiko Schocher, In message <[EMAIL PROTECTED]> you wrote: > Patch > http://git.denx.de/?p=u-boot.git;a=commitdiff;h=2a1a2cb6e2b87ee550e6f27b647d23331dfd5e1b#patch3 > > didnt remove the dummy mem reservation in fdt_chosen, and > this stopped Linux from booting with a Ramdisk. This patch > fixes this, by deleting the useless dummy mem reservation. > > When booting with a Ramdisk, a fix offset FDT_RAMDISK_OVERHEAD > is now added to of_size, so we dont need anymore a dummy > mem reservation. > > I measured the value of FDT_RAMDISK_OVERHEAD on a MPC8270 > based system (=0x44 bytes) and rounded it up to 0x80). > > Signed-off-by: Heiko Schocher <[EMAIL PROTECTED]> > --- > common/cmd_fdt.c |3 ++- > common/fdt_support.c |4 +--- > include/fdt.h |2 ++ > include/fdt_support.h |2 +- > lib_ppc/bootm.c |5 +++-- > 5 files changed, 9 insertions(+), 7 deletions(-) Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] The software required `Windows 95 or better', so I installed Linux. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH 1/1 V3] Add support for LZMA uncompression algorithm.
Dear Jean-Christophe PLAGNIOL-VILLARD, In message <[EMAIL PROTECTED]> you wrote: > --===0188417863== > > From: Luigi 'Comio' Mantellini <[EMAIL PROTECTED]> > > Signed-off-by: Luigi 'Comio' Mantellini <[EMAIL PROTECTED]> > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <[EMAIL PROTECTED]> > --- > Add missing lzma/Makefile > Makefile |1 + > README | 23 ++ > common/cmd_bootm.c | 23 ++ > common/image.c |1 + > include/image.h|1 + > include/lzma/LzmaDecode.h | 31 ++ > include/lzma/LzmaTools.h | 31 ++ > include/lzma/LzmaTypes.h | 31 ++ > lib_generic/lzma/LGPL.txt | 504 +++ > lib_generic/lzma/LzmaDecode.c | 584 +++ > lib_generic/lzma/LzmaDecode.h | 113 ++ > lib_generic/lzma/LzmaTools.c | 142 > lib_generic/lzma/LzmaTools.h | 35 ++ > lib_generic/lzma/LzmaTypes.h | 45 +++ > lib_generic/lzma/Makefile | 50 +++ > lib_generic/lzma/README.txt| 28 ++ > lib_generic/lzma/history.txt | 198 +++ > lib_generic/lzma/import_lzmasdk.sh | 38 ++ > lib_generic/lzma/lzma.txt | 663 > > 19 files changed, 2542 insertions(+), 0 deletions(-) > create mode 100644 include/lzma/LzmaDecode.h > create mode 100644 include/lzma/LzmaTools.h > create mode 100644 include/lzma/LzmaTypes.h > create mode 100644 lib_generic/lzma/LGPL.txt > create mode 100644 lib_generic/lzma/LzmaDecode.c > create mode 100644 lib_generic/lzma/LzmaDecode.h > create mode 100644 lib_generic/lzma/LzmaTools.c > create mode 100644 lib_generic/lzma/LzmaTools.h > create mode 100644 lib_generic/lzma/LzmaTypes.h > create mode 100644 lib_generic/lzma/Makefile > create mode 100644 lib_generic/lzma/README.txt > create mode 100644 lib_generic/lzma/history.txt > create mode 100644 lib_generic/lzma/import_lzmasdk.sh > create mode 100644 lib_generic/lzma/lzma.txt Applied, but please be abit more careful about Coding style requirements: Applying Add support for LZMA uncompression algorithm. .dotest/patch:414: trailing whitespace. .dotest/patch:779: trailing whitespace. .dotest/patch:786: trailing whitespace. It means that you can select one of these two licenses and .dotest/patch:790: trailing whitespace. Igor Pavlov, as the author of this Code, expressly permits you to .dotest/patch:791: trailing whitespace. statically or dynamically link your Code (or bind by name) to the warning: squelched 171 whitespace errors warning: 176 lines applied after fixing whitespace errors. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Space is big. You just won't believe how vastly, hugely, mind- bogglingly big it is. I mean, you may think it's a long way down the road to the drug store, but that's just peanuts to space. -- The Hitchhiker's Guide to the Galaxy ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Pull request: nand-flash
Dear Scott Wood, In message <[EMAIL PROTECTED]> you wrote: > The following changes since commit 0b7c5639891f4103a0e31ec7ae0beb3e97ed3836: > Heiko Schocher (1): > muas3001: update BR4 settings > > are available in the git repository at: > > git://www.denx.de/git/u-boot-nand-flash.git master > > Anton Vorontsov (3): > fsl_elbc_nand: fix OOB workability for large page NAND chips > fsl_elbc_nand: implement support for flash-based BBT > fsl_elbc_nand: ecclayout cleanups > > Hugo Villeneuve (1): > ARM DaVinci: Fix broken HW ECC for large page NAND. > > Scott Wood (1): > delta, zylonite: Update nand_oobinfo to nand_ecclayout. > > board/delta/nand.c |6 +-- > board/zylonite/nand.c|6 +-- > cpu/arm926ejs/davinci/nand.c | 81 +++-- > doc/README.nand |8 > drivers/mtd/nand/fsl_elbc_nand.c | 56 +++--- > 5 files changed, 138 insertions(+), 19 deletions(-) Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] No man knows what true happiness is until he gets married. By then, of course, its too late. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot for ixp425
Dear Martijn, in message <[EMAIL PROTECTED]> you wrote: > > We tried to get these patches in u-boot, but they where not accepted. "Were not accepted" is not quite correct. The patches you sent did not apply to the source tree and were somehow corrupted; also you failed to respond to the review comments. See http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/28148/focus=28409 and http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/29027 Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] "Success covers a multitude of blunders." - George Bernard Shaw ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Pull request: nand-flash
The following changes since commit 0b7c5639891f4103a0e31ec7ae0beb3e97ed3836: Heiko Schocher (1): muas3001: update BR4 settings are available in the git repository at: git://www.denx.de/git/u-boot-nand-flash.git master Anton Vorontsov (3): fsl_elbc_nand: fix OOB workability for large page NAND chips fsl_elbc_nand: implement support for flash-based BBT fsl_elbc_nand: ecclayout cleanups Hugo Villeneuve (1): ARM DaVinci: Fix broken HW ECC for large page NAND. Scott Wood (1): delta, zylonite: Update nand_oobinfo to nand_ecclayout. board/delta/nand.c |6 +-- board/zylonite/nand.c|6 +-- cpu/arm926ejs/davinci/nand.c | 81 +++-- doc/README.nand |8 drivers/mtd/nand/fsl_elbc_nand.c | 56 +++--- 5 files changed, 138 insertions(+), 19 deletions(-) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH 3/3] fsl_elbc_nand: ecclayout cleanups
From: Anton Vorontsov <[EMAIL PROTECTED]>
This patch deletes oobavail assignments, they're calculated by the nand
core code in nand_scan_tail, plus current oobavail values are wrong for
the LP NANDs.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: David Woodhouse <[EMAIL PROTECTED]>
Signed-off-by: Scott Wood <[EMAIL PROTECTED]>
---
>From the Linux driver, applied to u-boot-nand-flash.
drivers/mtd/nand/fsl_elbc_nand.c |4
1 files changed, 0 insertions(+), 4 deletions(-)
diff --git a/drivers/mtd/nand/fsl_elbc_nand.c b/drivers/mtd/nand/fsl_elbc_nand.c
index e4e4de0..4351824 100644
--- a/drivers/mtd/nand/fsl_elbc_nand.c
+++ b/drivers/mtd/nand/fsl_elbc_nand.c
@@ -95,7 +95,6 @@ static struct nand_ecclayout fsl_elbc_oob_sp_eccm0 = {
.eccbytes = 3,
.eccpos = {6, 7, 8},
.oobfree = { {0, 5}, {9, 7} },
- .oobavail = 12,
};
/* Small Page FLASH with FMR[ECCM] = 1 */
@@ -103,7 +102,6 @@ static struct nand_ecclayout fsl_elbc_oob_sp_eccm1 = {
.eccbytes = 3,
.eccpos = {8, 9, 10},
.oobfree = { {0, 5}, {6, 2}, {11, 5} },
- .oobavail = 12,
};
/* Large Page FLASH with FMR[ECCM] = 0 */
@@ -111,7 +109,6 @@ static struct nand_ecclayout fsl_elbc_oob_lp_eccm0 = {
.eccbytes = 12,
.eccpos = {6, 7, 8, 22, 23, 24, 38, 39, 40, 54, 55, 56},
.oobfree = { {1, 5}, {9, 13}, {25, 13}, {41, 13}, {57, 7} },
- .oobavail = 48,
};
/* Large Page FLASH with FMR[ECCM] = 1 */
@@ -119,7 +116,6 @@ static struct nand_ecclayout fsl_elbc_oob_lp_eccm1 = {
.eccbytes = 12,
.eccpos = {8, 9, 10, 24, 25, 26, 40, 41, 42, 56, 57, 58},
.oobfree = { {1, 7}, {11, 13}, {27, 13}, {43, 13}, {59, 5} },
- .oobavail = 48,
};
/*
--
1.5.6.rc1.6.gc53ad
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH 2/3] fsl_elbc_nand: implement support for flash-based BBT
From: Anton Vorontsov <[EMAIL PROTECTED]>
This patch implements support for flash-based BBT for chips working
through ELBC NAND controller, so that NAND core will not have to re-scan
for bad blocks on every boot.
Because ELBC controller may provide HW-generated ECCs we should adjust
bbt pattern and bbt version positions in the OOB free area.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: David Woodhouse <[EMAIL PROTECTED]>
Signed-off-by: Scott Wood <[EMAIL PROTECTED]>
---
>From the Linux driver, applied to u-boot-nand-flash.
drivers/mtd/nand/fsl_elbc_nand.c | 35 ++-
1 files changed, 34 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/nand/fsl_elbc_nand.c b/drivers/mtd/nand/fsl_elbc_nand.c
index b8bc143..e4e4de0 100644
--- a/drivers/mtd/nand/fsl_elbc_nand.c
+++ b/drivers/mtd/nand/fsl_elbc_nand.c
@@ -136,6 +136,34 @@ static struct nand_bbt_descr largepage_memorybased = {
.pattern = scan_ff_pattern,
};
+/*
+ * ELBC may use HW ECC, so that OOB offsets, that NAND core uses for bbt,
+ * interfere with ECC positions, that's why we implement our own descriptors.
+ * OOB {11, 5}, works for both SP and LP chips, with ECCM = 1 and ECCM = 0.
+ */
+static u8 bbt_pattern[] = {'B', 'b', 't', '0' };
+static u8 mirror_pattern[] = {'1', 't', 'b', 'B' };
+
+static struct nand_bbt_descr bbt_main_descr = {
+ .options = NAND_BBT_LASTBLOCK | NAND_BBT_CREATE | NAND_BBT_WRITE |
+ NAND_BBT_2BIT | NAND_BBT_VERSION,
+ .offs = 11,
+ .len = 4,
+ .veroffs = 15,
+ .maxblocks = 4,
+ .pattern = bbt_pattern,
+};
+
+static struct nand_bbt_descr bbt_mirror_descr = {
+ .options = NAND_BBT_LASTBLOCK | NAND_BBT_CREATE | NAND_BBT_WRITE |
+ NAND_BBT_2BIT | NAND_BBT_VERSION,
+ .offs = 11,
+ .len = 4,
+ .veroffs = 15,
+ .maxblocks = 4,
+ .pattern = mirror_pattern,
+};
+
/*=*/
/*
@@ -738,7 +766,12 @@ int board_nand_init(struct nand_chip *nand)
nand->waitfunc = fsl_elbc_wait;
/* set up nand options */
- nand->options = NAND_NO_READRDY | NAND_NO_AUTOINCR;
+ nand->bbt_td = &bbt_main_descr;
+ nand->bbt_md = &bbt_mirror_descr;
+
+ /* set up nand options */
+ nand->options = NAND_NO_READRDY | NAND_NO_AUTOINCR |
+ NAND_USE_FLASH_BBT;
nand->controller = &elbc_ctrl->controller;
nand->priv = priv;
--
1.5.6.rc1.6.gc53ad
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH 1/3] fsl_elbc_nand: fix OOB workability for large page NAND chips
From: Anton Vorontsov <[EMAIL PROTECTED]>
For large page chips, nand_bbt is looking into OOB area, and checking
for "0xff 0xff" pattern at OOB offset 0. That is, two bytes should be
reserved for bbt means.
But ELBC driver is specifying ecclayout so that oobfree area starts at
offset 1, so only one byte left for the bbt purposes.
This causes problems with any OOB users, namely JFFS2: after first mount
JFFS2 will fill all OOBs with "erased marker", so OOBs will contain:
OOB Data: ff 19 85 20 03 00 ff ff ff 00 00 08 ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
OOB Data: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
And on the next boot, NAND core will rescan for bad blocks, then will
see "0xff 0x19" pattern, and will mark all blocks as bad ones.
To fix the issue we should implement our own bad block pattern: just one
byte at OOB start. Though, this will work only for x8 chips. For x16
chips two bytes must be checked. Since ELBC driver does not support x16
NANDs (yet), we're safe for now.
Signed-off-by: Anton Vorontsov <[EMAIL PROTECTED]>
Signed-off-by: David Woodhouse <[EMAIL PROTECTED]>
Signed-off-by: Scott Wood <[EMAIL PROTECTED]>
---
>From the Linux driver, applied to u-boot-nand-flash.
drivers/mtd/nand/fsl_elbc_nand.c | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/drivers/mtd/nand/fsl_elbc_nand.c b/drivers/mtd/nand/fsl_elbc_nand.c
index 674c542..b8bc143 100644
--- a/drivers/mtd/nand/fsl_elbc_nand.c
+++ b/drivers/mtd/nand/fsl_elbc_nand.c
@@ -122,6 +122,20 @@ static struct nand_ecclayout fsl_elbc_oob_lp_eccm1 = {
.oobavail = 48,
};
+/*
+ * fsl_elbc_oob_lp_eccm* specify that LP NAND's OOB free area starts at offset
+ * 1, so we have to adjust bad block pattern. This pattern should be used for
+ * x8 chips only. So far hardware does not support x16 chips anyway.
+ */
+static u8 scan_ff_pattern[] = { 0xff, };
+
+static struct nand_bbt_descr largepage_memorybased = {
+ .options = 0,
+ .offs = 0,
+ .len = 1,
+ .pattern = scan_ff_pattern,
+};
+
/*=*/
/*
@@ -750,9 +764,10 @@ int board_nand_init(struct nand_chip *nand)
priv->fmr = (15 << FMR_CWTO_SHIFT) | (2 << FMR_AL_SHIFT);
- /* adjust Option Register and ECC to match Flash page size */
+ /* Large-page-specific setup */
if (or & OR_FCM_PGS) {
priv->page_size = 1;
+ nand->badblock_pattern = &largepage_memorybased;
/* adjust ecc setup if needed */
if ((br & BR_DECC) == BR_DECC_CHK_GEN) {
--
1.5.6.rc1.6.gc53ad
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] Inefficient code in NetLoop() ?
Dear Ben,
I just ran over this piece of code in NetLoop() [see "net/net.c"]:
286 int
287 NetLoop(proto_t protocol)
288 {
...
322 eth_halt();
323 #ifdef CONFIG_NET_MULTI
324 eth_set_current();
325 #endif
326 if (eth_init(bd) < 0) {
327 eth_halt();
328 return(-1);
329 }
Am I reading this correctly that we eth_halt() and eth_init() the
network interface for each and every call to NetLoop?
This looks terribly inefficient to me - is there any rationale behind
this?
Also, the eth_set_current() checking should IMHO be done just once,
before we start a network transfer, or when we actually switch
interfaces, but not for each and every call to NetLoop() ?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
All easy problems have already been solved.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] iMX31 nand driver
Hi, I'm designing a board that uses a i.MX31 and a Nand Flash conected to the Nand Flash controller of i.MX31. I use git to get latest revision of u-boot code, and apply the patches to get mx31 nand drivers from *Magnus Lilja *posted at *Wed Aug 6 14:19:20 CEST 2008* mailing list. I got u-boot + nand drivers compiled, but when I run it I got weird results when reading flash, like data is reading in reverse order in buffer. I think that, in a blank Flash, I would get 0x on starting addresses (0x), but i was getting 0x30303030. More strange is that if I read address 0xB800 after 'nand read', I'll get same content of buffer memory where I put the result of nand read. Below I put some capture what I did. Could you know told me if it is ok? Sincerely I suspect that is inverted on buffer. 0x30303030 code would must be on spare area of NANDFC. Regards, Fabio Nand chip is a Micron MT29F2G08AACWP: Page size x8: 2,112 bytes (2,048 + 64 bytes), Block size: 64 pages (128K + 4K bytes), Device size: 2Gb: 2,048 blocks; --- nand info Device 0: NAND 256MiB 3,3V 8-bit, sector size 128 KiB uboot> nand device 0 Device 0: NAND 256MiB 3,3V 8-bit... is now current device uboot> nand read 0x8000 0x0 0x2 NAND read: device 0 offset 0x0, size 0x2 131072 bytes read: OK uboot> md 0x8000 8000: 30303030 30303030 30303030 30303030 8010: 30303030 30303030 30303030 30303030 8020: 30303030 30303030 30303030 30303030 8030: 30303030 30303030 30303030 30303030 8040: 30303030 30303030 8050: 8060: 8070: 8080: 8090: 80a0: 80b0: 80c0: 80d0: 80e0: 80f0: uboot> 8100: 8110: 8120: 8130: 8140: 8150: 8160: 8170: 8180: 8190: 81a0: 81b0: 81c0: 81d0: 81e0: 81f0: uboot> 8200: 8210: 8220: 8230: 8240: 8250: 8260: 8270: 8280: 8290: 82a0: 82b0: 82c0: 82d0: 82e0: 82f0: uboot> 8300: 8310: 8320: 8330: 8340: 8350: 8360: 8370: f
Re: [U-Boot] u-boot for ixp425
On 21:18 Fri 12 Sep , Martijn de Gouw wrote: > Hi > > > Moreover I knew that quite recently, some improvements have > > been made on > > u-boot to avoid the use of Intel APIs. > > Now I don't know if this activity has been completely carried > > out and allows > > the use of both eth interfaces which are provided by the uP. > > Can anybody suggest me where can I find some further info on > > the status of > > u-boot on ixp425? > > We have u-boot running on a ixp425 board (pdnb3), without the intel > stuff. > The npe binaries are stored seperated in flash, and loaded by u-boot. > All the code is now gplv2. > > We tried to get these patches in u-boot, but they where not accepted. > > Maybe you want to take a look at our patches. It's already the case Best Regards, J. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot for ixp425
Hi > Moreover I knew that quite recently, some improvements have > been made on > u-boot to avoid the use of Intel APIs. > Now I don't know if this activity has been completely carried > out and allows > the use of both eth interfaces which are provided by the uP. > Can anybody suggest me where can I find some further info on > the status of > u-boot on ixp425? We have u-boot running on a ixp425 board (pdnb3), without the intel stuff. The npe binaries are stored seperated in flash, and loaded by u-boot. All the code is now gplv2. We tried to get these patches in u-boot, but they where not accepted. Maybe you want to take a look at our patches. Regards, Martijn de Gouw Disclaimer: The information contained in this email, including any attachments is confidential and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 1.3.4 and MPC8270 board
[sorry, message has been cut] Could this be a timing issue ? I don't see much timing in ep82xxm code for example. Or perhaps the MRW configuration is not enough to correctly configure burst mode ? (Of course I'm also new in SDRAM init...) Thanks for ELDK and U-Boot, they are really great. Best regards, Rémi Lefevre ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot 1.3.4 and MPC8270 board
U-Boot 1.3.4 (Sep 12 2008 - 19:16:33) MPC8270 Reset Status: External Soft, External Hard MPC8270 Clock Configuration - Bus-to-Core Mult 5x, VCO Div 2, 60x Bus Freq 20-60 , Core Freq 100-300 - dfbrg 0, corecnf 0x1b, busdf 6, cpmdf 1, plldf 0, pllmf 6, pcidf 3 - vco_out 583331000, scc_clk 145832750, brg_clk 145832750 - cpu_clk 416665000, cpm_clk 291665500, bus_clk 8000 CPU: MPC8270 (HiP7 Rev 14, Mask 1.0 1K49M) at 416.665 MHz Board: DMYx MPC8270 DRAM: 128 MB Well, I have to admit it was quite an emotion to see this the first time! Top of RAM usable for U-Boot at: 0800 Reserving 227k for U-Boot at: 07fc7000 Reserving 4224k for malloc() at: 07ba7000 Reserving 84 Bytes for Board Info at: 07ba6fac Reserving 76 Bytes for Global Data at: 07ba6f60 So far so good, but... Stack Pointer at: 07ba6f48 New Stack Pointer is: 07ba6f48 ?~??o (<- garbage characters then nothing) I can't say I'm surprised. I expected some trouble in the relocation. As others before me, the u-boot code is correctly copied in RAM, the code run from "in_ram:", but hangs in "trap_init:". >From the FAQ and mailing list, I would assume I hit the "99% relocation problems come from burst mode" issue. But I don't really know where to investigate. From the manual of my SDRAM (MT48LC16M16A2), the init sequence is very similar to eg. ep82xxm's one. Could this be a timing issue ? I don't see much timing in ep82xxm code for example. Or perhaps the MRW configuration is not enough to correctly configure burst mode ? (Of course I'm also new in SDRAM init...) Thanks for ELDK and U-Boot, they are really great. Best regards, Rémi Lefevre ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] embedded standalone app for AVR32
I suspected the linkerscript was the issue. Can anyone point me in the right direction to a correct linker script for my purposes or even a good online source on how to correctly edit or generate a linker scripts with regards to interrupts/heap/stack/etc allocation rules/guidelines?. I have tried editing these on my own (using scripts from Atmel, gnu script for the atap7000 chips, u-boot and freertos) with no luck. I'm having difficulty understanding why my app isn't working. I'm guessing I'm close but I'm missing a piece of this puzzle. Best regards, Sean Sean Flynn [EMAIL PROTECTED] Senior Software Engineer Hexagon Metrology, Inc Brown & Sharpe division 250 Circuit Drive North Kingstown, RI, 02852 phone: 1-401-886-2686 fax: 1-401-886-2228 www.HexagonMetrology.us -Original Message- From: Haavard Skinnemoen [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2008 5:17 AM To: FLYNN Sean Cc: u-boot@lists.denx.de Subject: Re: [U-Boot] embedded standalone app for AVR32 "FLYNN Sean" <[EMAIL PROTECTED]> wrote: > When I included the interrupts in this application I was receiving > __heap_start__ and __heap_end__ undefined (along with a few other minor > linking errors that I fixed due to gcc libraries that were not linked > in). I attempted to define these areas in the linkerscript and was able > to get my app to build but it would not run. I attempted many different > iterations defining the heap sections unsuccessfully. FWIW I also > attempted to allocate some memory using malloc to see if the heap was > the problem and that wouldn't run either. Please keep talking to support about this. It sounds like a problem with the linkerscript you're using and has nothing to do with u-boot. > Hopefully I made myself clear in this e-mail but my ultimate goal is to > run an embedded app under u-boot, exit and boot to linux. I don't think you can return to u-boot if you reprogram the interrupt controller, or alter any other hardware that u-boot is using. Haavard ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v3] powerpc: Fix bootm to boot up again with a Ramdisk
On Sep 11, 2008, at 1:11 AM, Heiko Schocher wrote: > Patch > http://git.denx.de/?p=u-boot.git;a=commitdiff;h=2a1a2cb6e2b87ee550e6f27b647d23331dfd5e1b#patch3 > > didnt remove the dummy mem reservation in fdt_chosen, and > this stopped Linux from booting with a Ramdisk. This patch > fixes this, by deleting the useless dummy mem reservation. > > When booting with a Ramdisk, a fix offset FDT_RAMDISK_OVERHEAD > is now added to of_size, so we dont need anymore a dummy > mem reservation. > > I measured the value of FDT_RAMDISK_OVERHEAD on a MPC8270 > based system (=0x44 bytes) and rounded it up to 0x80). > > Signed-off-by: Heiko Schocher <[EMAIL PROTECTED]> > --- > common/cmd_fdt.c |3 ++- > common/fdt_support.c |4 +--- > include/fdt.h |2 ++ > include/fdt_support.h |2 +- > lib_ppc/bootm.c |5 +++-- > 5 files changed, 9 insertions(+), 7 deletions(-) Acked-by: Kumar Gala <[EMAIL PROTECTED]> - k ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] u-boot for ixp425
Hi Ing.G.Morandi (Portatile) wrote: > Hi to all, > > I'd like to use u-boot lo load small applications program on a board based > on IXP425. My customer has used redboot to load linux over this board and > now He asked to me to write some applications to test the hardware. > I tought to use u-boot because I have no knowledge on redboot and because I > have already used u-boot over ixp425 few years ago. > Moreover I knew that quite recently, some improvements have been made on > u-boot to avoid the use of Intel APIs. > I have done some work on ixp465. I think that u-boot for ixp425 supports: - initialization - ethernet ( if you include firmware ) - flash device. I have used cfi for the ixp465 Regards Michael ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] File System
Dear "=?ISO-8859-1?Q?S=E9bastien_Chr=E9tien?=", In message <[EMAIL PROTECTED]> you wrote: > > I installed u-boot on my ppc board. How can I boot linux with a ide compact > flash ? Is ext2 supported by u-boot ? > If yes how can I mount a partition ? You probably want to read the manual first. If compact flash is supported or not depends on your board configuration. ext2 is available if enabled in your board config file. You do not mount anything in U-Boot. You use the respective "???load" command to load a file from a file system to ram. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] If some day we are defeated, well, war has its fortunes, good and bad. -- Commander Kor, "Errand of Mercy", stardate 3201.7 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] Makefile cleanup secound step Pull request
Dear Jean-Christophe PLAGNIOL-VILLARD,
In message <[EMAIL PROTECTED]> you wrote:
> Hi Wolfgang,
> Please pull
>
> The following changes since commit 0b7c5639891f4103a0e31ec7ae0beb3e97ed3836:
> Heiko Schocher (1):
> muas3001: update BR4 settings
>
> are available in the git repository at:
>
> git://git.denx.de/u-boot-arm.git Makefile-next
>
> Jean-Christophe PLAGNIOL-VILLARD (29):
> cmd_vfd: Move conditional compilation to Makefile
> common/Makefile: add core command section
> cmd_fdc: Move conditional compilation to Makefile
> cmd_mac: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_EEPROM in CONFIG_ENV_IS_IN_EEPROM
> env_eeprom: Move conditional compilation to Makefile
> cmd_eeprom: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_DATAFLASH in CONFIG_ENV_IS_IN_DATAFLASH
> env_dataflash: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_NAND in CONFIG_ENV_IS_IN_NAND
> env_nand: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_NVRAM in CONFIG_ENV_IS_IN_NVRAM
> env_nvram: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_ONENAND in CONFIG_ENV_IS_IN_ONENAND
> env_onenand: Move conditional compilation to Makefile
> rename CFG_ENV_IS_IN_SPI_FLASH in CONFIG_ENV_IS_IN_SPI_FLASH
> env_sf: Move conditional compilation to Makefile
> rename CFG_ENV_IS_NOWHERE in CONFIG_ENV_IS_NOWHERE
> env_nowhere: Move conditional compilation to Makefile
> rename environment.c in env_embedded.c to reflect is functionality
> cleanup use of CFG_ENV_IS_IN_FLASH
> rename CFG_ENV_IS_IN_FLASH in CONFIG_ENV_IS_IN_FLASH
> env_flash: Move conditional compilation to Makefile
> move cmd_get_data_size to command.c
> cmd_mem: Move conditional compilation to Makefile
> nvedit: rename error comment to CONFIG_ENV_IS_IN_
> rename CFG_ENV macros to CONFIG_ENV
> bootm arm/avr32/blackfin/microblaze/nios2/sh: remove no more need
> 'error' label
> ap325rxa: remove duplicate CONFIG_FLASH_CFI_DRIVER
>
...
> 830 files changed, 3978 insertions(+), 4050 deletions(-)
> rename common/{environment.c => env_embedded.c} (98%)
Applied, thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED]
"If a computer can't directly address all the RAM you can use, it's
just a toy." - anonymous comp.sys.amiga posting, non-sequitir
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] u-boot for ixp425
Hi to all, I'd like to use u-boot lo load small applications program on a board based on IXP425. My customer has used redboot to load linux over this board and now He asked to me to write some applications to test the hardware. I tought to use u-boot because I have no knowledge on redboot and because I have already used u-boot over ixp425 few years ago. Moreover I knew that quite recently, some improvements have been made on u-boot to avoid the use of Intel APIs. Now I don't know if this activity has been completely carried out and allows the use of both eth interfaces which are provided by the uP. Can anybody suggest me where can I find some further info on the status of u-boot on ixp425? Many thanks in advance Gianfranco ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] File System
Hello, I installed u-boot on my ppc board. How can I boot linux with a ide compact flash ? Is ext2 supported by u-boot ? If yes how can I mount a partition ? Thanks ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [PHP] Re: Problem with function
Jochem Maas wrote:
Jason Pruim schreef:
On Sep 12, 2008, at 9:34 AM, Nathan Rixham wrote:
Nathan Rixham wrote:
Jason Pruim wrote:
On Sep 12, 2008, at 8:53 AM, Nathan Rixham wrote:
Jason Pruim wrote:
nothing obvious to me.. so debug more!
[snip snip snip]
have to say this:
error_reporting( E_ALL ); at the top would help; + display_errors on
in php.ini and problem is probably due to duplciate variable/constant
definition in default.php or dbmysqliconnect.php
I could agree more... which is why I have this:
ini_set('error_reporting', E_ALL);
But the log isn't showing anything...
php.ini is what he said.
My error log for the site has this:
[Fri Sep 12 09:40:54 2008] [debug] mod_rewrite.c(1643): [client
192.168.0.253] mod_rewrite's internal redirect status: 0/10.
--
Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
11287 James St
Holland, MI 49424
www.raoset.com
[EMAIL PROTECTED]
display_errors in php.ini is what you want; makes life easier while
developing; and good to have E_STRICT and E_ALL set for err reporting;
then you can catch every tiny potential future bug as well :)
ps did you read the one about your bind variables being in the wrong
order and too many?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
Re: [U-Boot] [ppc4xx] Please pull git://www.denx.de/git/u-boot-ppc4xx.git
Dear Stefan Roese, In message <[EMAIL PROTECTED]> you wrote: > The following changes since commit 0b7c5639891f4103a0e31ec7ae0beb3e97ed3836: > Heiko Schocher (1): > muas3001: update BR4 settings > > are available in the git repository at: > > git://www.denx.de/git/u-boot-ppc4xx.git master > > Ricardo Ribalda Delgado (3): > ppc4xx: Fix in-tree build for ppc440-generic boards > ppc4xx: Fix compilation of v5fx30teval_flash > ppc4xx: Add .gitignore file to xilinx-ppc440 boards > > Stefan Roese (2): > ppc4xx: Fix SDRAM inititialization of multiple 405 based board ports > ppc4xx: Enable device tree (FDT) support in zeus board port > > Makefile |4 +- > board/amcc/taihu/taihu.c |9 > board/avnet/v5fx30teval/.gitignore |1 + > board/dave/PPChameleonEVB/PPChameleonEVB.c | 25 -- > board/esd/pci405/pci405.c | 31 > > board/quad100hd/quad100hd.c|5 > board/xilinx/ml507/.gitignore |1 + > board/xilinx/ppc440-generic/.gitignore |1 + > board/xilinx/ppc440-generic/config.mk |2 +- > board/zeus/zeus.c | 23 > cpu/ppc4xx/sdram.c | 14 +--- > include/configs/quad100hd.h|1 - > include/configs/zeus.h |6 + > 13 files changed, 22 insertions(+), 101 deletions(-) > create mode 100644 board/avnet/v5fx30teval/.gitignore > create mode 100644 board/xilinx/ml507/.gitignore > create mode 100644 board/xilinx/ppc440-generic/.gitignore Applied thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Remember, there's a big difference between kneeling down and bending over. - Frank Zappa ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ARM Pull Request
Dear Jean-Christophe PLAGNIOL-VILLARD, In message <[EMAIL PROTECTED]> you wrote: > Hi Wolfgang, > Please pull > The following changes since commit 0b7c5639891f4103a0e31ec7ae0beb3e97ed3836: > Heiko Schocher (1): > muas3001: update BR4 settings > > are available in the git repository at: > > git://git.denx.de/u-boot-arm.git master > > Adrian Filipi (1): > Set up SD/MMC OCR as comment describes. i.e. 3.2-3.4v. > > Andrew Dyer (3): > arm920t fix constant error in start.S > i.MX use u-boot baud rate and don't assume UART master clock > i.mx change get_timer(base) to return time since base > > Claudio Scordino (1): > Fix MACH_TYPE for the AT91RM9200DK board. > > Guennadi Liakhovetski (1): > i.MX31: document timer precision option > > Gururaja Hebbar K R (1): > ARM OMAP : Correct Invalid Timer Register Field Declaration in > omap1510.h & omap730.h > > Hugo Villeneuve (1): > ARM DaVinci: Remove duplicate code in cpu/arm926ejs/davinci/dp83848.c > > Jean-Christophe PLAGNIOL-VILLARD (1): > ARM: synchronize mach-types.h with linux 2.6.27-rc6 > > Jens Scharsig (1): > at91rm9200: fix errors with CONFIG_CMD_I2C_TREE > > Magnus Lilja (2): > i.MX31: Add reset_timer() and modify get_timer_masked(). > i.MX31: Make the SPI bus and chip select configurable for MC13783 > > Shinya Kuribayashi (1): > make: Remove redundant __ARM__ addition when cross-compiling on *BSD > > README.imx31| 13 + > board/atmel/at91rm9200dk/at91rm9200dk.c |2 +- > config.mk |9 - > cpu/arm1136/mx31/interrupts.c | 24 +- > cpu/arm920t/at91rm9200/i2c.c| 10 + > cpu/arm920t/imx/interrupts.c|2 +- > cpu/arm920t/imx/serial.c| 56 +- > cpu/arm920t/start.S |6 +- > cpu/arm926ejs/davinci/dp83848.c | 27 +- > cpu/pxa/mmc.c |4 +- > doc/README.mx31 | 19 + > drivers/rtc/mc13783-rtc.c |6 +- > include/asm-arm/mach-types.h| 3645 > +-- > include/configs/imx31_litekit.h |3 + > include/configs/mx31ads.h |3 + > include/configs/omap1510.h |2 +- > include/configs/omap730.h |2 +- > 17 files changed, 3648 insertions(+), 185 deletions(-) > create mode 100644 README.imx31 > create mode 100644 doc/README.mx31 > mode change 100644 => 100755 include/configs/omap1510.h > mode change 100644 => 100755 include/configs/omap730.h > > Best Regards, Applied, thanks. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] A star captain's most solemn oath is that he will give his life, even his entire crew, rather than violate the Prime Directive. -- Kirk, "The Omega Glory", stardate unknown ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot and ELDK
Wolfgang Denk wrote: > Dear Roman, > > In message <[EMAIL PROTECTED]> you wrote: [snip] >> How necessary is it to install ELDK in order to be able to compile >> U-Boot for non-PPC platform? > > It's not necessary. You can use any other (decent) tool chain as > well. The nice thing with the ELDk is that it comes ready-to-use, > well tested, and in indentical versions for ARM, MIPS, and PowerPC. > And it's not only a cross tool chain, but also the native run time > environment which will come in handy once you got U-Boot running and > go forward to porting Linux :-) To chime in 2c from rumor an innuendo (and some actual experience), some of the cross compilation tool builds are actually scripts that pull down sources from internet sites and apply patches (also pulled down from internet sites) to those sources. This is done every time you build the cross tools. You do not control the sources/patches. While this is excellent for staying up to date (bleeding edge) on the cross tool environment, the downside is that you cannot go back and re-create a given cross tool environment because yesterdays build may use a different version of the sources/patches than todays build. ELDK is a well packaged binary distribution (with full source available) that can be archived and (re)installed at any time in the future with predictable results. It also captures all the sources necessary to recreate a given version so you can rebuild version 4.0[1] and have it match the version 4.0 you used months/years ago. For some uses, this doesn't matter. For long term business use where you may have to reinstall your tool set long after it has been declared "obsolete", this is a vital difference. > Best regards, > > Wolfgang Denk > Thanks to denx.de for providing the ELDK, gvb [1] Theoretically ;-). Rebuilding from source in practice may be challenging. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH] MPC512x: reduce timeout waiting for Ethernet autonegotiation to 2.5s
Previous timeout was 50 seconds which is a pain to wait for if you
have a system with no ethernet cable attached. Reduce this to 2.5
seconds as a compomise between fast boot and time needed by the PHY.
Signed-off-by: Wolfgang Denk <[EMAIL PROTECTED]>
---
drivers/net/mpc512x_fec.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/mpc512x_fec.c b/drivers/net/mpc512x_fec.c
index 54283fb..7078c4e 100644
--- a/drivers/net/mpc512x_fec.c
+++ b/drivers/net/mpc512x_fec.c
@@ -364,7 +364,7 @@ int mpc512x_fec_init_phy (struct eth_device *dev, bd_t *
bis)
/*
* Wait for AN completion
*/
- timeout = 5;
+ timeout = 2500;
do {
udelay (1000);
--
1.5.4.2
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] embedded standalone app for AVR32
Wolfgang Denk wrote: > Dear Haavard Skinnemoen, > > In message <[EMAIL PROTECTED]> you wrote: >> I don't think you can return to u-boot if you reprogram the interrupt >> controller, or alter any other hardware that u-boot is using. > > You can, if you make sure to save the previous state before changing > it, and restore it before returning to U-Boot. > > Best regards, > > Wolfgang Denk IOW, if you sow mines as you leave basecamp, mark them very carefully on the map so that you can pick them all up again when you return or one of them will go *BANG*. :-O gvb ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ERROR: CTL:TIMEOUT - USB porting issue for UBoot on TEngine/SH7727
Hi Remy, Thank you for your helping. It worked well. Many thanks -- View this message in context: http://www.nabble.com/ERROR%3A-CTL%3ATIMEOUT---USB-porting-issue-for-UBoot-on-TEngine-SH7727-tp19411807p19453698.html Sent from the Uboot - Users mailing list archive at Nabble.com. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [T-Engine] UBoot configuration for T-Engine/SH7727 MS7727CP02 DevKit
Hi,
Yoshihiro Shimoda wrote:
>
>
> diff --git a/common/usb.c b/common/usb.c
> index 9502f39..1acf51d 100644
> --- a/common/usb.c
> +++ b/common/usb.c
> @@ -250,7 +250,10 @@ int usb_set_maxpacket(struct usb_device *dev)
>
> for(i=0; iconfig.bNumInterfaces;i++) {
> for(ii=0; iiconfig.if_desc[i].bNumEndpoints; ii++) {
> - ep = &dev->config.if_desc[i].ep_desc[ii];
> + struct usb_endpoint_descriptor tmp;
> + memcpy(&tmp, &dev->config.if_desc[i].ep_desc[ii],
> + sizeof(struct usb_endpoint_descriptor));
> + ep = &tmp;
> b=ep->bEndpointAddress & USB_ENDPOINT_NUMBER_MASK;
>
> if((ep->bmAttributes &
> USB_ENDPOINT_XFERTYPE_MASK)==USB_ENDPOINT_XFER_CONTROL) { /* Control =>
> bidirectional */
>
Thank you a lot, it worked well. :jumping::jumping::jumping::jumping:
Thank you for good instruction.
Best regards,
--
View this message in context:
http://www.nabble.com/-T-Engine--UBoot-configuration-for-T-Engine-SH7727-MS7727CP02-DevKit-tp18868090p19453640.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] embedded standalone app for AVR32
Dear Haavard Skinnemoen, In message <[EMAIL PROTECTED]> you wrote: > > I don't think you can return to u-boot if you reprogram the interrupt > controller, or alter any other hardware that u-boot is using. You can, if you make sure to save the previous state before changing it, and restore it before returning to U-Boot. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] Testing can show the presense of bugs, but not their absence. -- Edsger Dijkstra ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [T-Engine] UBoot configuration for T-Engine/SH7727 MS7727CP02 DevKit
Hi, thaoth
thaoth wrote:
> Can you help me to resolve this bug?
I think that it is a problem of the unalignment access.
Please change your compiler or change a source code as follows:
diff --git a/common/usb.c b/common/usb.c
index 9502f39..1acf51d 100644
--- a/common/usb.c
+++ b/common/usb.c
@@ -250,7 +250,10 @@ int usb_set_maxpacket(struct usb_device *dev)
for(i=0; iconfig.bNumInterfaces;i++) {
for(ii=0; iiconfig.if_desc[i].bNumEndpoints; ii++) {
- ep = &dev->config.if_desc[i].ep_desc[ii];
+ struct usb_endpoint_descriptor tmp;
+ memcpy(&tmp, &dev->config.if_desc[i].ep_desc[ii],
+ sizeof(struct usb_endpoint_descriptor));
+ ep = &tmp;
b=ep->bEndpointAddress & USB_ENDPOINT_NUMBER_MASK;
if((ep->bmAttributes &
USB_ENDPOINT_XFERTYPE_MASK)==USB_ENDPOINT_XFER_CONTROL) {/* Control =>
bidirectional */
> Thank you very much for your supports!
You're welcome! :)
Best regards,
Yoshihiro Shimoda
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [T-Engine] UBoot configuration for T-Engine/SH7727 MS7727CP02 DevKit
Hi Yoshihiro Shimoda,
* Strategy 1:
I add usb_cpu_init following your tutorial:
int usb_cpu_init(void)
{
*STCBR3 = 0x18;
*SRSTR = 0x18;
cpu_wait_ms(50);
*EXCPGCR = 0x21;//0x28;
*PECR = 0x1500;
cpu_wait_ms(50);
*SRSTR = 0x00;
*STCBR3 = 0x00;
return 0;
}
now, I plug the USB2.0(mass storage) into board T-Engine(sh7727) and run
command "usb start", the u-boot can't get decription of usb device with the
errror following:
New Device 1
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0
x8
set address 2
usb_control_msg: request: 0x5, requesttype: 0x0, value 0x2 index 0x0 length
0x0
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x100 index 0x0
length 0
x12
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0
x8
usb_control_msg: request: 0x6, requesttype: 0x80, value 0x200 index 0x0
length 0
x20
get_conf_no 0 Result 32, wLength 32
if 0, ep 0
if 0, ep 1
##EP epmaxpacketin[1] = 64
* Strategy 2:
I add usb_cpu_init the same strategy 1, I only add instruction "printf("&ep
= %x\n",&ep);" into function usb_set_maxpacket of usb.c
int usb_set_maxpacket(struct usb_device *dev)
{
.
...
ep = &dev->config.if_desc[i].ep_desc[ii];
b=ep->bEndpointAddress & USB_ENDPOINT_NUMBER_MASK;
printf("&ep = %x\n",&ep);
.
..
}
in this strategy, when I run command "usb start", now I can get information
of USB device:
Manufacturer
Product USB_DRIVE
SerialNumber 00106886
2 USB Device(s) found
scanning bus for storage devices... usb_control_msg: request: 0xFF,
reque
sttype: 0x21, value 0x0 index 0x0 length 0x0
usb_control_msg: request: 0x1, requesttype: 0x2, value 0x0 index 0x81 length
0x0
usb_control_msg: request: 0x1, requesttype: 0x2, value 0x0 index 0x2 length
0x0
1 Storage Device(s) found
I don't know what is problem?why when I add instruction "printf("&ep =
%x\n",&ep);", u-boot can get description of USB device
*Strategy 3:
I try replace the insctruction "printf("&ep = %x\n",&ep);" with one of these
instructions
- instruction 1: wait_ms(10)
- instruction 2:void * pointer = &ep;
- instruction 3: "printf("ep = %x\n",ep);"
But the result when run command "usb start" the same strategy 1, I can't get
information of USB2.0(mass storage)
Can you help me to resolve this bug?
Thank you very much for your supports!
Yoshihiro Shimoda wrote:
>
> Hi, thaoth.
>
> thaoth wrote:
>>
>> 0x28: 00101000 -> 00 101 000 ->
>> * 101: Using bus clock
>> * 000: Dividing Ratio Selection is 1/1
>>
>> I know
>> * Internal clock: 96Mhz
>> * Peripheral Clock: 24Mhz
>> * CPU Block: 144Mhz
>>
>> http://www.nabble.com/file/p19449833/a.JPG a.JPG
>>
>> Please let me know the correct value of EXCPGCR ? Is 0x28 correct
>> initialize
>> value of USB clock?
>
> I think that 0x21 is correct value of EXCPGCR for your board.
>
> 0x21: 00101000 -> 00 100 001 ->
> * 100: Using Internal Clock
> * 001: Dividing Ratio Selection is 1/2
> (96MHz / 2 = 48MHz)
>
>>> And I used my board, I set 0x1500 in PKCR.
>> I don't understand PKCR - Port control register so I don't know correct
>> initialize value of this register.
>>
>> 0x1500 = 0001 0101
>> -> PK6 is port output
>> -> PK5 is port output
>> -> PK4 is port output
>> I don't know this value could be set for my board - TEngine/SH7727.
>
> Oh, I am very sorry. This is PECR.
> This setting enable USB1_pwr_en and USB2_pwr_en pin.
>
> Best regards,
> Yoshihiro Shimoda
> ___
> U-Boot mailing list
> U-Boot@lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
>
--
View this message in context:
http://www.nabble.com/-T-Engine--UBoot-configuration-for-T-Engine-SH7727-MS7727CP02-DevKit-tp18868090p19453016.html
Sent from the Uboot - Users mailing list archive at Nabble.com.
___
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] embedded standalone app for AVR32
"FLYNN Sean" <[EMAIL PROTECTED]> wrote: > When I included the interrupts in this application I was receiving > __heap_start__ and __heap_end__ undefined (along with a few other minor > linking errors that I fixed due to gcc libraries that were not linked > in). I attempted to define these areas in the linkerscript and was able > to get my app to build but it would not run. I attempted many different > iterations defining the heap sections unsuccessfully. FWIW I also > attempted to allocate some memory using malloc to see if the heap was > the problem and that wouldn't run either. Please keep talking to support about this. It sounds like a problem with the linkerscript you're using and has nothing to do with u-boot. > Hopefully I made myself clear in this e-mail but my ultimate goal is to > run an embedded app under u-boot, exit and boot to linux. I don't think you can return to u-boot if you reprogram the interrupt controller, or alter any other hardware that u-boot is using. Haavard ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ctrl-c detection (on 4xx platforms)
Dear Matthias Fuchs, In message <[EMAIL PROTECTED]> you wrote: > > when I disable CONFIG_AUTOBOOT_KEYED ctrl-c checking is not disabled. I think there is one "dis" ot "not" too many. > We are using CONFIG_AUTOBOOT_KEYED to have a special key (SPACE) to > abort autoboot and not the 'any' key. I thought so. > Is there any special reason why ctrl-c checking is disabled for > CONFIG_AUTOBOOT_KEYED? Excellent question. Next question, please. I think the rationale behind this is to prevent users from getting an interactive prompt by just pressing ^C - the intention of CONFIG_AUTOBOOT_KEYED is similar to a login with password - without the correct password you are denied access to an interactive inter- face. But if you could use ^C as soon as the bootcmd has started - what should happen next? We cannot simply drop you into the interactive shell? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] When the ax entered the forest, the trees said, "The handle is one of us!" -- Turkish proverb ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] U-Boot and ELDK
Dear Roman, In message <[EMAIL PROTECTED]> you wrote: > > There are numerous toolchains and kits out there -- head's spinning. > ELDK is one of them. In my understanding ELDK focuses on PowerPC > architecture, but toolchains for ARM/MIPS architectures are also In theory, ELDK supports ARM, MIPS, and PowerPC likewise. Relaity is that we are customer driven, and normally new versions get ported PowerPC first, then ARM, and finally MIPS. You can see this right now: the PowerPC has been out for a couple of months, ARM is still a few weeks away, and MIPS also. > available. How reasonable is it to take it and use it for, let's say, > ARM9 based platform ? It's perfectly reasonable. We use only the ELDK four our work, on all ARM, MIPS, and PowerPC systems. > How necessary is it to install ELDK in order to be able to compile > U-Boot for non-PPC platform? It's not necessary. You can use any other (decent) tool chain as well. The nice thing with the ELDk is that it comes ready-to-use, well tested, and in indentical versions for ARM, MIPS, and PowerPC. And it's not only a cross tool chain, but also the native run time environment which will come in handy once you got U-Boot running and go forward to porting Linux :-) Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: [EMAIL PROTECTED] READ THIS BEFORE OPENING PACKAGE: According to Certain Suggested Ver- sions of the Grand Unified Theory, the Primary Particles Constituting this Product May Decay to Nothingness Within the Next Four Hundred Million Years. ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ctrl-c detection (on 4xx platforms)
Hi, when I disable CONFIG_AUTOBOOT_KEYED ctrl-c checking is not disabled. We are using CONFIG_AUTOBOOT_KEYED to have a special key (SPACE) to abort autoboot and not the 'any' key. Is there any special reason why ctrl-c checking is disabled for CONFIG_AUTOBOOT_KEYED? Matthias On Friday 12 September 2008 09:00, Matthias Fuchs wrote: > Hi Wolfgang, > > yes I do have CONFIG_AUTOBOOT_KEYED enabled. It's the PMC440 board: > > include/configs/PMC440.h: > ... > #define CONFIG_AUTOBOOT_KEYED 1 > #define CONFIG_AUTOBOOT_PROMPT\ > "Press SPACE to abort autoboot in %d seconds\n", bootdelay > #undef CONFIG_AUTOBOOT_DELAY_STR > #define CONFIG_AUTOBOOT_STOP_STR " " > ... > > Matthias > > > On Thursday 11 September 2008 22:55, Wolfgang Denk wrote: > > Dear Matthias Fuchs, > > > > In message <[EMAIL PROTECTED]> you wrote: > > > > > > I noticed some strange CTRL-C behavior in a BSP command. > > > When I run my bsp command interactively everything is fine. > > ... > > > But when I call this bsp command as bootcmd CTRL-C does not stop the > > > while loop. So CTRL-C > > > is not detected. Any idea? > > > > Do you happen to have CONFIG_AUTOBOOT_KEYED set in your board > > configuration? > > > > Best regards, > > > > Wolfgang Denk > > > ___ > U-Boot mailing list > U-Boot@lists.denx.de > http://lists.denx.de/mailman/listinfo/u-boot > > -- - Dipl.-Ing. Matthias Fuchs Head of System Design esd electronic system design gmbh Vahrenwalder Str. 207 - 30165 Hannover - GERMANY Phone: +49-511-37298-0 - Fax: +49-511-37298-68 Please visit our homepage http://www.esd.eu Quality Products - Made in Germany - Geschäftsführer: Klaus Detering, Dr. Werner Schulze Amtsgericht Hannover HRB 51373 - VAT-ID DE 115672832 - ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] ctrl-c detection (on 4xx platforms)
Hi Wolfgang, yes I do have CONFIG_AUTOBOOT_KEYED enabled. It's the PMC440 board: include/configs/PMC440.h: ... #define CONFIG_AUTOBOOT_KEYED 1 #define CONFIG_AUTOBOOT_PROMPT \ "Press SPACE to abort autoboot in %d seconds\n", bootdelay #undef CONFIG_AUTOBOOT_DELAY_STR #define CONFIG_AUTOBOOT_STOP_STR " " ... Matthias On Thursday 11 September 2008 22:55, Wolfgang Denk wrote: > Dear Matthias Fuchs, > > In message <[EMAIL PROTECTED]> you wrote: > > > > I noticed some strange CTRL-C behavior in a BSP command. > > When I run my bsp command interactively everything is fine. > ... > > But when I call this bsp command as bootcmd CTRL-C does not stop the while > > loop. So CTRL-C > > is not detected. Any idea? > > Do you happen to have CONFIG_AUTOBOOT_KEYED set in your board > configuration? > > Best regards, > > Wolfgang Denk > ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] U-Boot and ELDK
Hello. I apologize if my question sounds silly :) There are numerous toolchains and kits out there -- head's spinning. ELDK is one of them. In my understanding ELDK focuses on PowerPC architecture, but toolchains for ARM/MIPS architectures are also available. How reasonable is it to take it and use it for, let's say, ARM9 based platform ? How necessary is it to install ELDK in order to be able to compile U-Boot for non-PPC platform? Thanks. -- Roman Mashak ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
