From: Phil Sutter <n0-1@freewrt.org>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: Jeff Garzik <jeff@garzik.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: [PATCH] pata-rb532-cf: read and write data in 4-byte blocks
Date: Wed, 5 Nov 2008 13:52:47 +0100 [thread overview]
Message-ID: <20081105125247.GB14551@nuty> (raw)
In-Reply-To: <49118984.7090004@ru.mvista.com>
Hi,
On Wed, Nov 05, 2008 at 02:54:44PM +0300, Sergei Shtylyov wrote:
> Phil Sutter wrote:
>
> >Well, Sergei Shtylyov pointed out that the original driver does transfer
> >data at 4-byte blocks, so I changed it accordingly and tested it.
> >Hopefully this will provide a performance gain, though I did not do any
> >performance tests and therefore can't tell if that's really the case.
> >
>
> Might've been worth to put this into separate patch, apart from the
> fix for the function prototype.
Ok, I will do that.
> >I had interpreted Sergei's response to my BUG_ON() statement for it to
> >be unnecessary, which may be wrong.
>
> You misintepreted my response. :-)
Oh well, if only communication was as easy as programming C. :)
> >I don't know if it's possible to
> >connect ATAPI devices to the on board CompactFlash slot, maybe you can
>
> I don't think so.
What about those devices for PDAs like GPS mice or UMTS modems? The
platform for dangerous half knowledge talks about "CF I/O". Is this
something completely different?
> >give me some hints on this. OTOH I see that the sector size is hard
> >coded in the original driver to 0x200, so I guess either ATAPI is not
> >possible or at least not with the original driver, right?
>
> If ATAPI was indeed possible, BUG() wouldn't have been an option.
> I've just remembered about the READ/WRITE LONG commands which might
> cause byte count to not be divisible by 4 (although by default ECC is
> 4-byte entity and CF 1.4 says that this is the ony option).
Sure, I added it because it's an assumption made on the algorithm to
function correctly and I wasn't sure if that's the case.
So what's the final solution to this? Transfer byte-wise if buflen is
not a multiple of four (I doubt this would provide full ATAPI
compatibility, though I have no idea) or maybe transfer (buflen % 4)
bytes less and return something different than buflen?
I sadly don't have any hardware to test with other than a CF-disk, which
of course is an ATA device.
Thanks, Phil
next prev parent reply other threads:[~2008-11-05 12:51 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 21:47 [PATCH] fix pata-rb532-cf Phil Sutter
2008-10-30 22:39 ` Florian Fainelli
2008-10-30 23:20 ` Sergei Shtylyov
2008-10-31 0:09 ` Phil Sutter
2008-10-31 10:38 ` Sergei Shtylyov
2008-10-31 11:08 ` Sergei Shtylyov
2008-11-01 16:09 ` Phil Sutter
2008-11-01 16:12 ` Phil Sutter
2008-11-01 16:26 ` Sergei Shtylyov
2008-11-01 16:45 ` Sergei Shtylyov
2008-11-01 16:45 ` Phil Sutter
2008-11-01 18:09 ` Phil Sutter
2008-11-01 18:11 ` [PATCH] read and write data in 4-byte blocks Phil Sutter
2008-11-01 18:21 ` Phil Sutter
2008-11-02 21:23 ` Sergei Shtylyov
2008-11-03 13:29 ` [PATCH] pata-rb532-cf: " Phil Sutter
2008-11-03 13:45 ` Bartlomiej Zolnierkiewicz
2008-11-04 6:01 ` Jeff Garzik
2008-11-04 12:35 ` Phil Sutter
2008-11-05 11:54 ` Sergei Shtylyov
2008-11-05 12:52 ` Phil Sutter [this message]
2008-11-02 22:04 ` [PATCH] fix pata-rb532-cf Sergei Shtylyov
2008-11-02 22:45 ` Phil Sutter
2008-11-01 16:16 ` Sergei Shtylyov
2008-11-12 0:13 ` Phil Sutter
2008-11-12 0:13 ` [PATCH] pata-rb532-cf: read/write data in 4-byte blocks Phil Sutter
2008-11-12 0:14 ` [PATCH] pata-rb532-cf: fix signature of the xfer function Phil Sutter
2008-11-12 2:26 ` Florian Fainelli
2008-11-12 10:54 ` Sergei Shtylyov
2008-11-12 2:25 ` [PATCH] pata-rb532-cf: read/write data in 4-byte blocks Florian Fainelli
2008-11-12 10:50 ` Sergei Shtylyov
2008-11-12 20:57 ` [PATCH] fix pata-rb532-cf Bartlomiej Zolnierkiewicz
2008-11-14 23:53 ` Jeff Garzik
2009-01-11 16:13 ` Florian Fainelli
2009-01-11 20:47 ` Phil Sutter
2009-01-12 14:32 ` Florian Fainelli
2009-01-12 17:48 ` Phil Sutter
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=20081105125247.GB14551@nuty \
--to=n0-1@freewrt.org \
--cc=bzolnier@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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