From: Nicholas Wourms <nwourms@myrealbox.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: Re: 2.4.21-rc1-ac2 Promise IDE DMA won't work
Date: Tue, 29 Apr 2003 20:21:39 -0400 [thread overview]
Message-ID: <3EAF1713.7000009@myrealbox.com> (raw)
In-Reply-To: 200304291841.38501.tabris@sbcglobal.net
Tabris wrote:
> On Tuesday 29 April 2003 04:15 pm, Andre Hedrick wrote:
>
>>The Promise chipset use a second DMA engine at offset 0x24 respective
>>of the channel. Mixing an ATA and ATAPI on that channel is almost
>>impossible to make the corner cases work. Next, if there us a 48-bit
>>ATA plus ATAPI on the channel popping between the two enignes does
>>not look sane at all because one has to swithc the location of the
>>hwif->sgtable.
>
>
> Ok... moved the HDDs from the VIA secondary to the PDC primary (tried
> moving both, but it seems that ide=reverse doesn't work), and the
> CD-R/W to the VIA secondary.
>
> good news, regular reads seem to use the DMA engine. bad news, CDDA
> ripping (using cdparanoia) does not.
>
> is this a known issue? (i thought that CDDA ripping had been fixed)
>
Have you tried Andrew Morton's ide-cd dma patch? It seems to have
worked well for me, at least. A summary of what it does is included at
the top of the patch.
http://www.zipworld.com.au/~akpm/linux/patches/2.4/2.4.20/ide-akpm.patch
Perhaps Alan might considier it for the -rc2 ac patch?
Cheers,
Nicholas
next prev parent reply other threads:[~2003-04-30 0:14 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
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 [this message]
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=3EAF1713.7000009@myrealbox.com \
--to=nwourms@myrealbox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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