From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND driver updates
Date: Thu, 10 Jan 2008 06:45:01 +0100 [thread overview]
Message-ID: <200801100645.01940.sr@denx.de> (raw)
In-Reply-To: <200801100003.06519.matthias.fuchs@esd-electronics.com>
Hi Matthias,
On Thursday 10 January 2008, Matthias Fuchs wrote:
> I tested your updated NAND repo on a PLU405 board (405EP with small block
> NAND attached to EBC+GPIOs).
>
> I found two more issues and incompatibilities against the current mainline
> code:
>
> 1) The new code is much more noisy during startup:
> Old:
> ...
> DRAM: 32 MB
> FLASH: 1 MB
> NAND: 32 MiB
> PCI: Bus Dev VenId DevId Class Int
> ...
>
> New:
> ...
> FLASH: 1 MB
> NAND: NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung NAND
> 32MiB 3,3V 8-bit) Scanning device for bad blocks
> Bad eraseblock 261 at 0x00414000
> Bad eraseblock 352 at 0x00580000
> Bad eraseblock 846 at 0x00d38000
> Bad eraseblock 848 at 0x00d40000
> 32 MiB
> PCI: Bus Dev VenId DevId Class Int
> ...
>
> Perhaps we should calme is down by using the option 'CFG_NAND_QUIET_TEST'.
> Also the formatting of the output is not very pretty.
Yes, we should remove those lines. I suggest to use debug() for here, so that
they are printed when DEBUG is defined.
> 2) 'nand read.jffs2' and 'nand read.i' do not read anything.
> 'nand read' is ok. Are there any boards where you tested this ok?
No, I didn't test this. IIRC there is still a TODO in the source that this
still has to be implemented/tested. It shouldn't be that hard though. I would
really appreciate it if you (or somebody else) could take a look at this.
Thanks.
BTW: I'm not available today.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2008-01-10 5:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 15:54 [U-Boot-Users] [PATCH] NAND: Change nand_wait_ready() to not call nand_wait() Stefan Roese
2008-01-05 16:15 ` [U-Boot-Users] NAND driver updates Stefan Roese
2008-01-08 10:05 ` Matthias Fuchs
2008-01-08 22:06 ` ksi at koi8.net
2008-01-13 7:24 ` Dirk Behme
2008-01-13 8:14 ` ksi at koi8.net
2008-01-09 23:03 ` Matthias Fuchs
2008-01-10 5:45 ` Stefan Roese [this message]
2008-01-10 17:46 ` Stefan Roese
2008-01-15 8:49 ` Stefan Roese
2008-01-15 12:34 ` Matthias Fuchs
2008-01-15 12:48 ` Stig A. Olsen
2008-01-15 17:56 ` ksi at koi8.net
2008-01-16 13:45 ` Stefan Roese
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=200801100645.01940.sr@denx.de \
--to=sr@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.