From: Ed Sweetman <safemode@comcast.net>
To: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: libata ignores non-dma disks?
Date: Tue, 21 Mar 2006 21:19:37 -0500 [thread overview]
Message-ID: <4420B439.6000608@comcast.net> (raw)
I'm using 2.6.16-rc6-ide1 (alan's patchset) and using the sata_nv and
pata_amd drivers. I have all UDMA drives except a CF disk -> IDE
interface, which should be running in PIO mode4. Libata detects the
device, but spits out a message about "no dma" and then says it's not
supported and is ignoring it. Is this device not supported because
it's not using dma or for some other reason?
It's the only device on it's channel (secondary pata)
ata6: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xF008 irq 15
ata6: dev 0 cfg 49:0e00 82:0000 83:0000 84:0000 85:0000 86:0000 87:0000
88:0000
ata6: no dma
ata6: dev 0 not supported, ignoring
scsi5 : pata_amd
I'd really like to get this up and running so if anyone has any
suggestions, I'm all ears.
next reply other threads:[~2006-03-22 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 2:19 Ed Sweetman [this message]
2006-03-22 11:48 ` [PATCH] libata: do not ignore PIO-only devices Tejun Heo
2006-03-22 12:47 ` Tejun Heo
2006-03-23 0:58 ` Jeff Garzik
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=4420B439.6000608@comcast.net \
--to=safemode@comcast.net \
--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 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).