All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: David Schleef <ds@schleef.org>
Cc: mtd@infradead.org
Subject: Re: sharp driver dissimilarities
Date: Sat, 28 Apr 2001 17:11:57 +0100	[thread overview]
Message-ID: <17699.988474317@redhat.com> (raw)
In-Reply-To: <20010428090021.A21620@stm.lbl.gov>


ds@schleef.org said:
>  I tried and failed, but that may be just my lack of understanding of
> the CFI driver.  The commands, command write locations, and status
> bits have no similarity to other chip drivers.

The commands certainly have some similarity with the cfi_cmdset_0001 code, 
which isn't particularly surprising as command set 0001 is 'Intel/Sharp'.

However, at the time you did sharp.c, I believe that CFI code wasn't 
sufficiently generic to deal with 4x8-bit chips. It ought to manage that 
now, though.

        /* Clear the status register first */
        cfi_write(map, CMD(0x50), adr);

        /* Now erase */
        cfi_write(map, CMD(0x20), adr);
        cfi_write(map, CMD(0xD0), adr);

We really ought to separate the backends which actually drive the chips from 
the probe code.

--
dwmw2




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

  reply	other threads:[~2001-04-28 16:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-26 15:55 Power blackouts and brownouts Vipin Malik
2001-04-27  7:39 ` Joakim Tjernlund
2001-04-27 14:30   ` Vipin Malik
2001-04-27 14:34     ` David Woodhouse
2001-04-27 15:31       ` Vipin Malik
2001-04-27 20:37       ` David Schleef
2001-04-28 10:34         ` David Woodhouse
2001-04-28 16:00           ` sharp driver dissimilarities David Schleef
2001-04-28 16:11             ` David Woodhouse [this message]
2001-04-28 17:15               ` David Schleef
2001-04-28 17:26                 ` 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=17699.988474317@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=ds@schleef.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.