public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Michel Stempin" <mstempin@com1.fr>
To: "mtd" <linux-mtd@lists.infradead.org>
Subject: RE: Block device as MTD
Date: Thu, 28 Jun 2001 09:39:03 +0200	[thread overview]
Message-ID: <NEBBLPFMELCDALFMOJILAEDGCGAA.mstempin@com1.fr> (raw)

Hi,

I found in the past some very good data sheets from SanDisk and Hitachi
(among others). Of course, they are not the original specs, but they provide
some very usefull application examples.

CF and PCMCIA flash are very similar in programming: both can be used either
as an IDE drive, or as a raw flash device. I don't remember if it's a pin
selection or an init command that triggers the mode change.

--
Michel Stempin
MIS
COM One SA, 11 parc de Marticot, 33610 CESTAS, FRANCE
Tel: +33(0)5 57 97 72 72
Fax: +33(0)5 56 78 84 78
Email: mstempin@com1.fr

> -----Message d'origine-----
> De : linux-mtd-admin@lists.infradead.org
> [mailto:linux-mtd-admin@lists.infradead.org]De la part de Simon Evans
> Envoyé : jeudi 28 juin 2001 00:03
> À : Felix Radensky
> Cc : linux-mtd@lists.infradead.org
> Objet : Re: Block device as MTD
>
>
>
> Hi,
>
> Basically it wont work. blkmtd isnt actually a driver more a translation
> layer. If you want to talk to CF cards directly, you'll have to write an
> MTD driver for it. I dont know much about CF cards as I have always used
> them as IDE drives, but you may want to look at the PCMCIA utils memory_cs
> driver. I think CF cards can appear as regular PCMCIA flash memory cards
> until a bit is enabled that puts them into IDE mode.
>
> I tried a test once using the memory_cs driver on a CF and whilst it
> gave me some memory regions, they werent the correct size. Basically,
> you'll have to do some hacking around on the driver to get it to work
> but I dont know where to find specs for CF cards.
>
> the PCMCIA stuff is at http://pcmcia-cs.sourceforge.net/
>
> My next project is to write an MTD driver for PCMCIA flash cards
> (not CF) and if I get that working, im going to try and have a go at
> CF after that.
>
> cheers
> si
>
> >Hi,
> >
> >We have CF slot on our board, but no IDE controllers. Can I
> still use your
> >blkmtd.c driver to access CF ? If not, what approach should I take to
> >utilize
> >CF (adding IDE controller is not an option) ?
> >
> >Thanks in advance.
> >
> >Felix.
> >
> >
> >
> >______________________________________________________
> >Linux MTD discussion mailing list
> >http://lists.infradead.org/mailman/listinfo/linux-mtd/
> >
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

             reply	other threads:[~2001-06-28  7:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28  7:39 Michel Stempin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-26 10:33 Block device as MTD Simon Evans
2001-06-26 18:22 ` Tim Riker
2001-06-26 20:19 ` Simon Evans
2001-06-26 21:41   ` Bao C. Ha
2001-06-26 20:58     ` Simon Evans
2001-06-26 23:12   ` kira brown
2001-06-26 23:32     ` Bao C. Ha
2001-06-27  6:49   ` Felix Radensky
2001-06-27 22:03     ` Simon Evans
2001-06-27 23:41       ` Bill Roman

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=NEBBLPFMELCDALFMOJILAEDGCGAA.mstempin@com1.fr \
    --to=mstempin@com1.fr \
    --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