linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "dezheng shen" <dzshen@winbond.com>
To: linux-scsi@vger.kernel.org
Subject: [Winbond] MS/MS Pro driver for Winbond 528 PCI reader for public review
Date: Tue, 27 Jun 2006 16:07:59 +0800	[thread overview]
Message-ID: <44A0E75F.4090800@winbond.com> (raw)

Dear all:
   This email was originally posted on linux-kernel but I didn't get any 
response yet so that I post it to this linux-scsi again. Hope that we 
can get reply soon.

thank you,

dz

Dear all:
   Eventually, we found a place to place our sources for public review.

   Files are located in

http://zeniv.linux.org.uk/~winbond/

and they have been tested on Intel/AMD single/dual processors and Redhat 
9/Fedora 5 and Redhat workstation 4. We ran a stress test on multiple 
platforms overnight to read/write/format MS/MSPro cards via Winbond 528 
readers.

   Our customers, motherboard manufactures like ASUS, purchase Winbond 
528 then mount their motherboards. Winbond 528 itself provides many 
reader functions like MS/MSPro/SM/xD/SD/MMC and Winbond also vendors 
many other different chips for various buses. For example, Winbond 518 
is for LPC bus and 488 is for embedded hooked up to data bus directly. 
Our team is to derive a simple and unified architecture so that we don't 
have to write redudant codes for each chip, like 518/528/528DA and 488. 
Another example is, wbtable.c and wbtable.h are also used on xD/SM drivers.

   Someone might wonder why we use SCSI subsystem to implement those 
device drivers? When we are assigned this job in 2004, the previous 
engineer has been working on this device driver for over a year and 
he/she was using SCSI subsystem and we don't know why and we simply 
follow her/his trace to deliver this driver to our customers as soon as 
we can. Also, when we plug similar USB flash memory readers, it shows 
sda/sdb so that we took the same approach as SCSI devices.

   Don't hesitate to ask if you have any questions.

best regards,

dz



===========================================================================================
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.

             reply	other threads:[~2006-06-27  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  8:07 dezheng shen [this message]
2006-07-28 22:42 ` [Winbond] MS/MS Pro driver for Winbond 528 PCI reader for public review James Bottomley

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=44A0E75F.4090800@winbond.com \
    --to=dzshen@winbond.com \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).