Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Hello, Sergei. Sergei Shtylyov wrote: >Heh, it works by accident: PIO4 timings correspond to MWDMA ones. The > driver does *not* support MWDMA modes -- there's FIXME in > ali_set_dma_mode(). Yeap, I saw that and lifted MWDMA programming from pata_ali. That's how I got the identical PCI confi

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Mark Lord wrote: > Are you really sure that the old IDE is actually issuing DMA commands, > rather than falling back to PIO ? Yeap, pretty sure. Here is debug dump of IDE transferring sector zero. [ 114.377898] XXX writing 0x8 to dma_cmd [ 114.381718] XXX read dma_stat 0x24 and writing 0x26 [

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Alan Cox wrote: >> trying to fix it for some time now && finally got a machine with >> pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. > > Oh good. I've been through a pile of ones that just work. > > Which North and south does it have and what revision ? Attached full o

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Hello, Bartlomiej Zolnierkiewicz wrote: >> I wondered whether the device was configured differently, so compared >> hdparm --Istdout results. They were identical too. (attached) > > ATA device, with non-removable media > Model Number: IC25N040ATMR04-0 > Serial Number:

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Bartlomiej Zolnierkiewicz
Hi Tejun, On Wednesday 09 January 2008, Tejun Heo wrote: > Hello, all. > > Broken MWDMA on pata_ali has caused a number of bug reports. I've been > trying to fix it for some time now && finally got a machine with > pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. > Test

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Alan Cox
On Wed, 9 Jan 2008 17:16:35 + Alan Cox <[EMAIL PROTECTED]> wrote: > > trying to fix it for some time now && finally got a machine with > > pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. > > Oh good. I've been through a pile of ones that just work. > > Which North an

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Sergei Shtylyov
Tejun Heo wrote: Hello, all. Broken MWDMA on pata_ali has caused a number of bug reports. I've been trying to fix it for some time now && finally got a machine with pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. Testing confirms what users have been reporting - MWDMA2

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Mark Lord
Are you really sure that the old IDE is actually issuing DMA commands, rather than falling back to PIO ? Cheers - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Alan Cox
> trying to fix it for some time now && finally got a machine with > pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. Oh good. I've been through a pile of ones that just work. Which North and south does it have and what revision ? > I walked through IDE and libata codes a

Re: [CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Oh... I forgot to mention something. I traced DMA command execution and the following is what happens. 1. host setups DMA engine (programs BMDMA controller) 2. host issues PACKET 3. device sets BSY 4. host transfers CDB when BSY clears and DRQ sets (Status turns to 0xd0) 5. host activates BMDMA e

[CALL-FOR-HELP] pata_ali: can't get MWDMA working!

2008-01-09 Thread Tejun Heo
Hello, all. Broken MWDMA on pata_ali has caused a number of bug reports. I've been trying to fix it for some time now && finally got a machine with pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago. Testing confirms what users have been reporting - MWDMA2 works fine with th