From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: linux-ide@vger.kernel.org
Subject: SATA DVD issue...
Date: Mon, 09 Aug 2010 16:22:07 +0200 [thread overview]
Message-ID: <4C600F0F.2010102@kernelconcepts.de> (raw)
Hello!
I am trying to use a SATA DVD burner on a Marvell Kirkwood based
platform, kernel is currently based on vanilla 2.6.34 with only board
specific patches.
SATA in general works just fine with harddisks.
But when I attach my DVD drive any data read or write access triggers a
BUG() in libata-sff.c:
ata_bmdma_qc_issue():
...
/* see ata_dma_blacklisted() */
BUG_ON((ap->flags & ATA_FLAG_PIO_POLLING) &&
qc->tf.protocol == ATAPI_PROT_DMA);
...
Command access (e.g. to eject the media or to erase a R/W disc) do work.
My knowledge about ATA and SATA is quite limited so I cannot really
interpret this issue.
After some looking around and with the hint in the comment I tried
blacklisting my drive, so I added an entry to libata-core.c:
{ "HL-DT-ST DVDRAM GH22LS50", "TL01", ATA_HORKAGE_NODMA },
Now the drive works but it is awefully slow - reading just a little over
1MB/s - well, without DMA mode this is quite expectable.
I suspect that the Marvell SATA host driver should be OK and is not in
fault - it is widely used in PCI setups and the SOC variant does almost
not differ. And I also suspect that the above "fix" is not the best way
to do it.
I also tried the same driver with a USB-SATA connector (I do not have a
SATA PC at hand right now) and there it behaves pretty normal with 5 to
10 times higher read rates.
I would be more than happy if someone could help me diagnosing and
especially fixing this problem. If I can give more information or try
different things on the board just let know!
Many thanks in advance!
Cheers
nils
--
kernel concepts GbR Tel: +49-271-771091-12
Sieghuetter Hauptweg 48 Fax: +49-271-771091-19
D-57072 Siegen Mob: +49-176-21024535
http://www.kernelconcepts.de
reply other threads:[~2010-08-09 14:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C600F0F.2010102@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=linux-ide@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 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.