From: Pierre Ossman <drzeus-list@drzeus.cx>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: MMC performance
Date: Mon, 18 Oct 2004 21:26:13 +0200 [thread overview]
Message-ID: <417418D5.60901@drzeus.cx> (raw)
In-Reply-To: <416ACA91.6040405@drzeus.cx>
I've solved (sort of) the problem with corrupt data when doing multiple
block writes. It seems the spec I have for the host controller isn't
quite correct when it comes to clock frequencies.
Copying the value that Windows uses (it doesn't adapt to the card) got
the card working perfectly. This value is (according to my spec) invalid
though. I need to hook up an oscilloscope to the device to figure this
one out.
Russell, the users of my driver have tested the write multiple block
patch and haven't run into any problems. If you haven't found any issues
I suggest making it standard.
Rgds
Pierre
next prev parent reply other threads:[~2004-10-18 19:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 11:05 MMC performance Pierre Ossman
2004-10-11 12:19 ` Russell King
2004-10-11 13:18 ` Alan Cox
2004-10-11 15:27 ` Pierre Ossman
2004-10-11 18:01 ` Pierre Ossman
2004-10-18 19:26 ` Pierre Ossman [this message]
2004-10-11 13:49 ` Pierre Ossman
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=417418D5.60901@drzeus.cx \
--to=drzeus-list@drzeus.cx \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.