From: Thomas Backlund <tmb@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc1-ac2 Promise IDE DMA won't work
Date: Tue, 29 Apr 2003 12:21:19 +0300 [thread overview]
Message-ID: <b8lg4a$dhk$1@main.gmane.org> (raw)
In-Reply-To: 200304282234.59745.tabris@sbcglobal.net
Tabris wrote:
> On Monday 28 April 2003 09:58 pm, Andre Hedrick wrote:
>> NO ATAPI DMA!
>>
>> I will not write the driver core to attempt to support the various
>> combinations. The ATAPI DMA engine space is used support 48bit.
>> Use the onboard controller for ATAPI.
>> Andre Hedrick
>> LAD Storage Consulting Group
>
> Can I object that it came built onto the board? okok... i'll take that
> as a no for now...
>
> Tho i'm still not quite sure how it makes a diff to be honest, unless
> you mean that the Promise and HPT will never be supported for DMA?
>
> and the only other thing i should say is that altho i'm not exactly a
> n00b, the average user WILL expect it to work.
>
> can i expect this to be fixed by 2.6? (yeah, i know... 2.4-ac-ide code
> is similar to 2.5-ide code)
> --
> tabris
The point is that you should put your ATAPI device (in this case the cd-rom)
on the VIA controllers, and place the hdd's on the promise controller,
since dma is supported for hdd's...
This is also their intended primary functions by the manufacturers...,
for example the HPT370 controller with bios version >1.1.x.xxx does
not have ATAPI support (atleast officially, I haven't tried it)
Thomas
next prev parent reply other threads:[~2003-04-29 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 1:12 2.4.21-rc1-ac2 Promise IDE DMA won't work Tabris
2003-04-29 1:58 ` Andre Hedrick
2003-04-29 2:34 ` Tabris
2003-04-29 9:21 ` Thomas Backlund [this message]
2003-04-29 20:15 ` Andre Hedrick
2003-04-29 20:55 ` Alan Cox
2003-04-29 22:41 ` Tabris
2003-04-30 0:21 ` Nicholas Wourms
2003-04-29 18:48 ` Tabris
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='b8lg4a$dhk$1@main.gmane.org' \
--to=tmb@iki.fi \
--cc=linux-kernel@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