All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Ossman <drzeus-list@drzeus.cx>
To: dezheng shen <dzshen@winbond.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	PI14 SJIN <SJin@winbond.com>
Subject: Re: [Winbond] flash memory reader SCSI device drivers [headers]
Date: Fri, 16 Jun 2006 08:07:26 +0200	[thread overview]
Message-ID: <44924A9E.6060601@drzeus.cx> (raw)
In-Reply-To: <44920B22.4030507@winbond.com>

dezheng shen wrote:
>> PS. I have a question regarding the W83L518 hardware, but haven't been
>> able to get in touch with the right people. Perhaps you have some
>> pointers?
>
>    anything about Winbond 518/528/528DA drivers, send email to
> dzshen@winbond.com which is ME.....
>

Well, this wasn't about this driver but about some other piece of
Winbond hardware for which I have written a driver (drivers/mmc/wbsd.c).

The things I need to know are:

 * How does the hardware determine which MMC commands are data
transfers? It would seem it has a (incomplete) list of opcodes internally.

 * Is it a known hardware bug that the FIFO usage bits in the FSR
register always read as zero?

Rgds
Pierre


  parent reply	other threads:[~2006-06-16  6:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13  9:37 [Winbond] flash memory reader SCSI device drivers dezheng shen
2006-06-13  9:58 ` Jesper Juhl
2006-06-14  6:03   ` dezheng shen
2006-06-14  7:54   ` dezheng shen
2006-06-15 19:02     ` Pierre Ossman
2006-06-16  1:36       ` [Winbond] flash memory reader SCSI device drivers [headers] dezheng shen
2006-06-16  2:32         ` Randy.Dunlap
2006-06-16  6:03         ` Pierre Ossman
2006-06-16  6:39           ` dezheng shen
2006-06-16 10:21             ` Jesper Juhl
2006-06-16  6:07         ` Pierre Ossman [this message]
2006-06-16  1:38       ` [Winbond] flash memory reader SCSI device drivers [C sources] dezheng shen

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=44924A9E.6060601@drzeus.cx \
    --to=drzeus-list@drzeus.cx \
    --cc=SJin@winbond.com \
    --cc=dzshen@winbond.com \
    --cc=linux-kernel@vger.kernel.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.