From: Sean Kelley <sean.sweng@gmail.com>
To: linux-mtd@lists.infradead.org
Subject: Linux MTD and NFTL - Question
Date: Mon, 14 Feb 2005 20:47:56 -0600 [thread overview]
Message-ID: <43507b7c0502141847134e1e68@mail.gmail.com> (raw)
I've been looking into an NFTL implementation for a device that uses a
NAND part and needs to be mounted on a Window's PC Desktop. Thus I
need a Block Device interface so as to present a surface on which a
FAT filesystem can be placed. However, in the course of my research
it came to my attention that a company called M-Systems has a hefty
amount of IP with regards to FTL and NFTL for pseudo-block devices.
How does the Linux MTD-NFTL skirt the patents that M-Systems has in
place? If I want to sell my product commercially what sort of risk?
It is not terribly clear. I've looked at YAFFS and JFFS2, but those
won't work if I wish to support USB mass storage for the Windows
desktop.
Any comments on NFTL and M-Systems patents much appreciated.
Thanks,
Sean
next reply other threads:[~2005-02-15 2:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 2:47 Sean Kelley [this message]
2005-02-15 7:48 ` Linux MTD and NFTL - Question David Woodhouse
2005-02-15 14:07 ` Sean Kelley
2005-02-15 14:39 ` David Woodhouse
2005-02-16 2:21 ` Sean Kelley
2005-02-15 14:33 ` Simon Haynes
2005-02-16 4:11 ` Sean Kelley
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=43507b7c0502141847134e1e68@mail.gmail.com \
--to=sean.sweng@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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