public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Jason Gunthorpe <jgg@deltatee.com>
Cc: mtd@infradead.org
Subject: Re: Compile problems
Date: Mon, 26 Jun 2000 07:45:54 +0100	[thread overview]
Message-ID: <25426.962001954@cygnus.co.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.1000625165745.15303B-100000@white.priv.deltatee.com>


jgg@deltatee.com said:
>  BTW, I am almost finished redoing my JEDEC stuff to be more like your
> CFI stuff [turns out my SIMM was made in 1995, no CFI] and adding
> support for interleved and banked memories.. will send you a patch
> soon. 

Like my CFI stuff will be when I've finished it, I assume - not like it is 
at the moment - busy waiting and only detecting one chip in a mapping :)

I'm going to protect each chip with its own spinlock, and make erases 
asynchronous. I was hoping to do that last week, but it doesn't seem to 
have happened. Maybe this week.

--
dwmw2




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

  parent reply	other threads:[~2000-06-26  6:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-24 22:24 Compile problems Jason Gunthorpe
2000-06-25 10:11 ` David Woodhouse
2000-06-25 23:08   ` Jason Gunthorpe
2000-06-26  6:44     ` David Woodhouse
2000-06-26  8:35       ` Jason Gunthorpe
2000-06-26  6:45     ` David Woodhouse [this message]
2000-06-26  8:37       ` Jason Gunthorpe
  -- strict thread matches above, loose matches on Subject: below --
2000-11-02 17:19 Problems with AMD CFI chips mark.langsdorf
2000-11-03 18:29 ` Compile problems Gregory Schallert
2000-11-04  2:20   ` 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=25426.962001954@cygnus.co.uk \
    --to=dwmw2@infradead.org \
    --cc=jgg@deltatee.com \
    --cc=mtd@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