From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Martin Rogge <marogge@onlinehome.de>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Mark Lord <liml@rtr.ca>,
linux-ide@vger.kernel.org
Subject: Re: Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23?
Date: Sat, 20 Oct 2007 00:26:23 +0400 [thread overview]
Message-ID: <471912EF.4020208@ru.mvista.com> (raw)
In-Reply-To: <200710192158.03836.marogge@onlinehome.de>
Hello.
Martin Rogge wrote:
>> BTW, can you try adding #define DEBUG to the driver meanwhile?..
> Yoda said: Try not. Do or do not. There is no try.
:-)
> So I did it. To be precise, I #defined both DEBUG and CMD_DEBUG. However, I am
> not sure the result is conclusive.
> On a good kernel I get a lot of lines of the type
> hda: dma_stat: 0x24 irq_stat: 0x44 mask: 0x04
> hdc: dma_stat: 0x24 irq_stat: 0x5c mask: 0x10
Yeah, this is what's emitted by the dma_end() method which used
CFR/ARTTIM23 PCI config. regs. to chack the interrupt status.
> and variations thereof. On a broken kernel the middle part changes to
> hda: dma_stat: 0x24 mrdmode: 0x00 mask: 0x04
Hm... this means that the chip doesn't work as documented in the spec,
i.e. MRDMODE reg. seems write only, like on older chips. Could you post the
output of 'lspci -v'?
> Hope this is of any help,
It is of great help. :-)
> cu Martin
MBR, Sergei
next prev parent reply other threads:[~2007-10-19 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200710142211.03382.marogge@onlinehome.de>
2007-10-15 17:14 ` Fwd: CMD 64x regression from 2.6.21 to 2.6.22 and 2.6.23? Sergei Shtylyov
[not found] ` <200710152339.33718.marogge@onlinehome.de>
2007-10-16 11:53 ` Sergei Shtylyov
2007-10-16 12:43 ` Mark Lord
2007-10-16 12:59 ` Sergei Shtylyov
2007-10-16 22:14 ` Bartlomiej Zolnierkiewicz
2007-10-17 19:15 ` Martin Rogge
2007-10-17 20:40 ` Sergei Shtylyov
2007-10-19 19:58 ` Martin Rogge
2007-10-19 20:26 ` Sergei Shtylyov [this message]
2007-10-19 23:09 ` Martin Rogge
2007-10-20 14:55 ` Sergei Shtylyov
2007-10-20 17:11 ` Sergei Shtylyov
2007-10-21 20:55 ` Martin Rogge
2007-10-26 15:38 ` Sergei Shtylyov
2007-10-18 22:39 ` Martin Rogge
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=471912EF.4020208@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=bzolnier@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=marogge@onlinehome.de \
/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).