linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Use IGN_SIMPLEX for ALi
Date: Wed, 13 May 2009 16:15:37 +0200	[thread overview]
Message-ID: <200905131615.38013.bzolnier@gmail.com> (raw)
In-Reply-To: <20090513144904.1fd2cca9@lxorguk.ukuu.org.uk>

On Wednesday 13 May 2009 15:49:04 Alan Cox wrote:
> > [ Sigh, this issue seems to go back to:
> > 
> >   commit 669a5db411d85a14f86cd92bc16bf7ab5b8aa235
> >   Author: Jeff Garzik <jeff@garzik.org>
> >   Date:   Tue Aug 29 18:12:40 2006 -0400
> > 
> >     [libata] Add a bunch of PATA drivers. ]
> 
> No its quite recent actually - broke around 2.6.27
> 
> The libata drivers try and reset the simplex bits to check if a device is
> merely in simplex mode by configuration. Unfortunately on the ALi if you
> put the device into a power saving mode and bring it back the simplex
> bits get corrupted and the register becomes unwritable (even to restore)
> 
> Somewhere around 2.6.27 something started rudely dumping the device into
> power saving mode outside of the ATA layer on certain PCs.
> 
> So we switch to ignoring the bit in the first place on this chip.

Ok, thanks for explaining it.

BTW you may consider removing ata_pci_bmdma_clear_simplex() call
from ali_init_chipset() now (before somebody decides to fix the code
to check the former's function return value).

      reply	other threads:[~2009-05-13 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-13 13:59 [PATCH] libata: Use IGN_SIMPLEX for ALi Alan Cox
2009-05-13 13:32 ` Bartlomiej Zolnierkiewicz
2009-05-13 13:49   ` Alan Cox
2009-05-13 14:15     ` Bartlomiej Zolnierkiewicz [this message]

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=200905131615.38013.bzolnier@gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jeff@garzik.org \
    --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).