From: Trevor Woerner <ppc339@vtnet.ca>
To: linas@austin.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: can't write
Date: Fri, 30 May 2003 07:09:59 -0400 [thread overview]
Message-ID: <200305300710.00024.ppc339@vtnet.ca> (raw)
In-Reply-To: <20030529100632.A22378@forte.austin.ibm.com>
On May 29, 2003 11:06 am, you wrote:
> On Wed, May 28, 2003 at 11:19:27PM -0400, Trevor Woerner wrote:
> > contains are zeros.
>
> presumably, you tried two different cards & controllers, to rule out
> a hardware failure?
Thanks for your help and suggestions!
I discovered the problem with writing yesterday, a byte-swapping issue
was causing the LBA address to be inserted into the registers
incorrectly. So it was writing, just not to the sector Linux was
calculating. I'm handling registers 6 and 7 as special cases so the ATA
command was always correct, but not the LBA address!
As you suggested, a hardware issue was at the heart of the "lost
interrupt" problem I was getting. A CF card manufactured by Canon
worked perfectly with no interrupt problem, SanDisk CF cards (as well
as Kingston) don't appear to generate interrupts between the transfer
of each sector in a multi-sector read or write. I think there's a
setting (ATA command) I can look into, and I think there's something in
the 'ide_drive_t' structure to play with (two members starting with
"mult_"). I could also modify the code to create N single sector
read/writes from single read/writes of N sectors.
So everything appears to be working fine, thanks for everyone's help!!
Trevor
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-05-30 11:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 3:19 can't write Trevor Woerner
[not found] ` <20030529100632.A22378@forte.austin.ibm.com>
2003-05-30 11:09 ` Trevor Woerner [this message]
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=200305300710.00024.ppc339@vtnet.ca \
--to=ppc339@vtnet.ca \
--cc=linas@austin.ibm.com \
--cc=linuxppc-dev@lists.linuxppc.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).