public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Savin Zlobec <savin@epico.si>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] AT91RM9200 NAND support
Date: Tue, 20 Jun 2006 11:07:46 +0200	[thread overview]
Message-ID: <4497BAE2.3010602@epico.si> (raw)
In-Reply-To: <1150790417.6780.107.camel@localhost.localdomain>

Thomas Gleixner wrote:

>On Tue, 2006-06-20 at 09:43 +0200, Savin Zlobec wrote:
>  
>
>>I'am working on this right now. I've changed the at91 driver and I'am 
>>going to
>>test it when I finish the changes on YAFFS - read/write_ecc and oobblock are
>>not part of mtd_info any more...
>>
>>I'am attaching the at91_nand.c changes.
>>    
>>
>
>Sorry, I doubt that any of these changes will actually work. The patch
>below might save your time.
>  
>
Thanks (I did a quick diff of other nand drivers, but missed the #error...).

I've put the kernel with latest mtd on my board and got the following:

Nand is recognized as 'NAND device: Manufacturer ID: 0x98, Chip ID: 0x75 
(Toshiba NAND 32MiB 3,3V 8-bit)',
should be 'NAND device: Manufacturer ID: 0xec, Chip ID: 0x75 (Samsung 
NAND 32MiB 3,3V 8-bit)'.

No bad blocks are detected at initial nand scan, but when running 
flash_eraseall all blocks are found bad.

  parent reply	other threads:[~2006-06-20  8:58 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20  6:54 [PATCH] AT91RM9200 NAND support Andrew Victor
2006-06-20  7:08 ` Thomas Gleixner
2006-06-20  7:17   ` Andrew Victor
2006-06-20  7:43     ` Savin Zlobec
2006-06-20  8:00       ` Thomas Gleixner
2006-06-20  8:08         ` Thomas Gleixner
2006-06-20  9:07         ` Savin Zlobec [this message]
2006-06-20  9:18           ` Thomas Gleixner
2006-06-20 10:49             ` Savin Zlobec
2006-06-20 11:12               ` Thomas Gleixner
2006-06-20 11:42                 ` Savin Zlobec
2006-06-20 11:55                   ` Thomas Gleixner
2006-06-20 12:28                     ` Savin Zlobec
2006-06-20 12:44                       ` Thomas Gleixner
2006-06-20 12:52                         ` Thomas Gleixner
2006-06-20 13:17                           ` Savin Zlobec
2006-06-20 13:01                         ` Savin Zlobec
2006-06-20 13:21                           ` Thomas Gleixner
2006-06-20 13:48                             ` Savin Zlobec
2006-06-20 13:57                               ` Thomas Gleixner
2006-06-20 14:24                                 ` Savin Zlobec
2006-06-20 14:24                                   ` Thomas Gleixner
2006-06-20 14:29                                   ` Thomas Gleixner
2006-06-20 15:53                                     ` Savin Zlobec
2006-06-20 15:53                                       ` Thomas Gleixner
2006-06-20 16:03                                         ` Savin Zlobec
2006-06-20  9:07   ` David Woodhouse
2006-06-20  9:14     ` Thomas Gleixner

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=4497BAE2.3010602@epico.si \
    --to=savin@epico.si \
    --cc=linux-mtd@lists.infradead.org \
    --cc=tglx@linutronix.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