public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PATA driver patch for 2.6.17
Date: Thu, 22 Jun 2006 20:50:33 +0400	[thread overview]
Message-ID: <200606222050.34248.arvidjaar@mail.ru> (raw)
In-Reply-To: <1150925002.15275.128.camel@localhost.localdomain>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 22 June 2006 01:23, Alan Cox wrote:
> Ar Maw, 2006-06-20 am 21:12 +0400, ysgrifennodd Andrey Borzenkov:
> > Running vanilla 2.6.17 + ide1 patch on ALi M5229 does not find CD-ROM.
> > Notice "ata2: command 0xa0 timeout" below.
>
> Not sure immediately but does the following help
>

Not really. AFAIK lowest nibble bit has meaning only in DMA mode anyway.

Anything else I could try to help pinpoint the problem?

> --- ../libata-devo/drivers/scsi/pata_ali.c	2006-06-20 11:50:15.000000000
> +0100 +++ drivers/scsi/pata_ali.c	2006-06-21 21:42:27.458542280 +0100
> @@ -181,11 +181,12 @@
>  	u8 fifo;
>  	int shift = 4 * adev->devno;
>
> -	/* Bits 3:2 (7:6 for slave) control the PIO. 00 is off 01
> -	   is on. The FIFO must not be used for ATAPI. We preserve
> -	   BIOS set thresholds */
> +	/* ATA - FIFO on set nibble to 0x05, ATAPI - FIFO off, set nibble to
> +	   0x00. Not all the docs agree but the behaviour we now use is the
> +	   one stated in the BIOS Programming Guide */
> +
>  	pci_read_config_byte(pdev, pio_fifo, &fifo);
> -	fifo &= ~(0x0C << shift);
> +	fifo &= ~(0x0F << shift);
>  	if (on)
>  		fifo |= (on << shift);
>  	pci_write_config_byte(pdev, pio_fifo, fifo);
> @@ -261,10 +262,10 @@
>
>  	/* PIO FIFO is only permitted on ATA disk */
>  	if (adev->class != ATA_DEV_ATA)
> -		ali_fifo_control(ap, adev, 0);
> +		ali_fifo_control(ap, adev, 0x00);
>  	ali_program_modes(ap, adev, &t, 0);
>  	if (adev->class == ATA_DEV_ATA)
> -		ali_fifo_control(ap, adev, 0x04);
> +		ali_fifo_control(ap, adev, 0x05);
>
>  }
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFEmspZR6LMutpd94wRApEgAJ4q7AQM09lZ/uTnSPJIM296LYnF9QCgp63W
5lygD8TmjYh+1QwOGTWbQkg=
=SDOQ
-----END PGP SIGNATURE-----

  reply	other threads:[~2006-06-22 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-19 18:15 PATA driver patch for 2.6.17 Alan Cox
2006-06-19 19:46 ` Marcus Furlong
2006-06-19 21:07   ` Alan Cox
2006-06-19 21:40     ` Marcus Furlong
2006-06-20  5:41     ` Fabio Comolli
2006-06-20  6:53       ` Alan Cox
2006-06-20 17:12 ` Andrey Borzenkov
2006-06-21 21:23   ` Alan Cox
2006-06-22 16:50     ` Andrey Borzenkov [this message]
2006-06-23 15:24       ` Alan Cox
2006-06-23 17:20         ` Andrey Borzenkov
2006-06-25 10:58     ` Andrey Borzenkov
2006-06-25 15:23 ` Kevin Radloff
2006-06-28 15:25   ` Kevin Radloff
2006-06-28 15:48     ` Alan Cox

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=200606222050.34248.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --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