public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Miguel Freitas" <miguel@cetuc.puc-rio.br>
To: sjhill@cotw.com
Cc: mtd@infradead.org
Subject: Re: ATTN DOC Developers!
Date: Thu, 14 Sep 2000 13:25:05 GMT-3	[thread overview]
Message-ID: <4D6F1F4C32@mamao.cetuc.puc-rio.br> (raw)


   Hi Steve,

> I am working with David on some CVS changes as well as a MTD
> system architecture diagram. It was brought to my attention
> that the DOC drivers (2000 and Millenium) are being merged
> into one driver (file). Who is currently responsible for this
> effort? Please reply ASAP. Thanks a bunch.
> 
> -Steve

   I have merged the two drivers into the current CVS as doc2000.c, 
but my resources are scard for testing it (I don't have any Millenium 
here). I also included support for 2Mb and 64Mb nand chips, and 
checked all timing requirements from the m-system specifications. 
All requirements should be ok now, there was some minor 
corrections on the older code, mostly on addressing and chip 
selection.
   BTW, I'm a little busy right now implementing DOC routines on a 
OS less microcontroler, but I'm still waiting for reports on the new 
driver. Please let me know any problem you may have.
   As you may see in some message from last month, there are 
some ideas for changing some MTD/DOC API...we could check it 
with you MTD system architecture diagram. (take a look at "New 
DiskOnChip Driver" and "ECC and multi page read write support" 
messages)


Regards,

Miguel Freitas
Center for Telecommunications Studies
CATHOLIC UNIVERSITY - BRASIL
e-mail: miguel@cetuc.puc-rio.br
phone/fax#:+55-21-540-8854


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

             reply	other threads:[~2000-09-14 16:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-14 16:25 Miguel Freitas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-09-11 16:45 ATTN DOC Developers! Steven J. Hill
2000-09-12  0:38 ` Ollie Lho

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=4D6F1F4C32@mamao.cetuc.puc-rio.br \
    --to=miguel@cetuc.puc-rio.br \
    --cc=mtd@infradead.org \
    --cc=sjhill@cotw.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