From: Mike Kilburn <mkilburn@ftel.net>
To: David.Woodhouse@mvhi.com
Cc: Linux-MTD mailing list <mtd@imladris.demon.co.uk>
Subject: Re[2]: RFC: kernel-based PCMCIA ...
Date: Tue, 18 May 1999 07:03:45 -0700 (PDT) [thread overview]
Message-ID: <199905181403.HAA02853@devel.ftel.com> (raw)
In-Reply-To: <E10kQCS-0001AQ-00@devel2.axiom.internal>
David Woodhouse <David.Woodhouse@mvhi.com> wrote:
>
> My main concern at the moment is producing a standalone driver for the
> DoC2000,
> with FTL built-in to it, for embedded systems using the 2.0 kernel. As soon
> as
> I've done that, I'll be turning back to the generic subsystem design, and
> producing a DoC2000 driver for the new system.
Is there any beta code available for this. We have a PC104 with a 4M boot
flash from M-Systems. The vendor of the PC104 wont give us any hardware
details on accessing the Flash and they say they are working with M-Systems
to have a driver in a month or so. We dont want to be dependent on them for
a driver.
>
> As an aside - we may have patent problems with using FTL on anything other
> than PCMCIA devices. Our position on this is as yet undecided.
> I've suggested that perhaps the flags for each low-level device should
> include
> a PCMCIA/ NON-PCMCIA bit, and the default configuration of the FTL driver
> should refuse to work with non-PCMCIA devices. I don't really know what else
> we
> can do.
Why would a PCMICA be any different than a Flash on a PC104 cpu card?
To unsubscribe, send "unsubscribe mtd" to majordomo@imladris.demon.co.uk
next prev parent reply other threads:[~1999-05-20 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-20 10:37 RFC: kernel-based PCMCIA David Woodhouse
1999-05-18 14:03 ` Mike Kilburn [this message]
1999-06-05 2:41 ` Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
1999-05-20 14:27 Re[2]: " David Woodhouse
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=199905181403.HAA02853@devel.ftel.com \
--to=mkilburn@ftel.net \
--cc=David.Woodhouse@mvhi.com \
--cc=mtd@imladris.demon.co.uk \
/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