public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jamey Hicks <jamey@crl.dec.com>
Cc: "'Trevor Woolven'" <trevw@zentropix.com>, MTD <mtd@infradead.org>
Subject: Re: TODO List
Date: Sat, 29 Apr 2000 01:27:59 +0100	[thread overview]
Message-ID: <26113.956968079@server.axiom.internal> (raw)
In-Reply-To: <D1674834F25BD3118B3208002BB90CD4440250@yen.crl.dec.com>



jamey@crl.dec.com said:
>  What's wrong with FTL?

Technically, there are two main problems.

Firstly, it's broken - it works for a while and then seems to corrupt the
 FTL. I can't see how I did that in porting David Hinds' code to use the MTD
flash access routines - so it could be an SMP issue (I'm testing on SMP) or it
could be because I'm testing on the RAM device, which calls the 'erase done'
callback directly from within the erase routine..

Secondly, it makes no attempt to handle byte-swapping - so if you run it on a 
BE machine, then your FTL is all BE, which doesn't conform to the spec, and 
obviously won't be portable to LE machines. We need to pepper it with 
cpu_to_le16() and le16_to_cpu() all over the place.

> What's the state of it wrt licensing M-Systems patents? 

M-Systems have a patent which covers FTL, but they've given a licence to use 
it on all PCMCIA devices. They have not granted a licence to use it with 
non-PCMCIA devices.

>  Can it be used for systems with onboard flash? 

I assume that's not actually the question you meant to ask.

Can it be used? Yes - although you'd do better to use JFFS.
May it be used? Only if you live in the Free World.



--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  parent reply	other threads:[~2000-04-29  0:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-28 11:52 TODO List Jamey Hicks
2000-04-28 12:17 ` Trevor Woolven
2000-04-29  0:27 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-04-28  8:38 Trevor Woolven

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=26113.956968079@server.axiom.internal \
    --to=dwmw2@infradead.org \
    --cc=jamey@crl.dec.com \
    --cc=mtd@infradead.org \
    --cc=trevw@zentropix.com \
    /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