From: Simon Haynes <simon@baydel.com>
To: tglx@linutronix.de, linux-mtd@lists.infradead.org
Subject: Re: New NAND interface
Date: Mon, 10 May 2004 17:35:47 +0100 [thread overview]
Message-ID: <D9A158B823BE@baydel.com> (raw)
In-Reply-To: <200405101732.23971.tglx@linutronix.de>
On Monday 10 May 2004 4:32 pm, Thomas Gleixner wrote:
> On Monday 10 May 2004 16:04, Simon Haynes wrote:
> > I explained, recently, on #mtd, that jffs2 was generating bad crc
>
> Yep. I explained this in
> http://lists.infradead.org/pipermail/linux-mtd/2004-April/009632.html
>
Sorry, I should have looked at the archives. This makes it all clear to me.
> > moment I have fixed this in my NAND driver by specifying autooob with the
> > useecc field set to 0.
>
> Sorry, I was not aware that you have a block driver for SM-FAT. Is this
> driver available anywhere ?
>
I have spoken to David about this and I am more than happy to provide the
source to anyone. David, kindly, suggested I send the code to him and he
would have a look before integrating it into the CVS system. I have not sent
it to David as there are restrictions which would not make it suitable for
all. I had planned to remove these and tidy things up but I just have not
made the time.
> > Firstly I am concerned that this might cause problems with other users of
> > the NAND driver. Is there cause for concern ?
>
> AFAIK, are JFFS2 and YAFFS the only clients of NAND driver, except your
> SSFDC module.
>
I guess JFFS2 and YAFFS will not bothered about my NAND driver doing auto
placement as they have their own schemes ?
> Secondly my SSFDC layer will only work with my NAND driver.
> If you have more questions feel free to ask or let me have a look into the
> code so I can give you more detailed hints.
>
As I said, I will supply you the code but I do not expect you to support it
and I do regard it as, incomplete, for gereral use.
> Thomas
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
Thomas,
Thankyou for your support, again :-). At some time I will look into how I can
change the SSFDC layer to interface properly to mtd/nand. As my frig seems to
work for now I am inclined to go with it, unless you think this otherwise.
Cheers
Simon.
next prev parent reply other threads:[~2004-05-10 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-10 14:04 New NAND interface Simon Haynes
2004-05-10 15:32 ` Thomas Gleixner
2004-05-10 16:35 ` Simon Haynes [this message]
2004-05-11 8:53 ` Thomas Gleixner
2004-05-11 9:47 ` Simon Haynes
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=D9A158B823BE@baydel.com \
--to=simon@baydel.com \
--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