linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@linux-foundation.org, linux-ide@vger.kernel.org,
	alan@lxorguk.ukuu.org.uk
Subject: Re: [patch 10/10] libata: fix (hopefully) all the remaining problems with devices failing setup/identify
Date: Tue, 23 Oct 2007 16:35:49 +0900	[thread overview]
Message-ID: <471DA455.2030909@gmail.com> (raw)
In-Reply-To: <4703FF2E.5080409@garzik.org>

Jeff Garzik wrote:
> akpm@linux-foundation.org wrote:
>> From: Alan <alan@lxorguk.ukuu.org.uk>
>>
>> Two fixes in this test patch.  One of them allows old CF cards to refuse
>> pio mode setting, and one to wait for the drive to settle after a set
>> features changes the speed settings, which is based upon the workarounds
>> used by drivers/ide.
>>
>> Please test and report back if you have an afflicted system.  This patch
>> isn't for merging just testing.
>>
>> The CF card fix will still display errors when the card works (got fixes
>> for that once I know the cure works) but should then be found/usable.
>>
>> Not signed off by anyone, not for merging
> 
> applied to libata-dev.git#for-testing, a throwaway branch for things
> like this

(It has been quite some time.  I'm catching up after a series of family
events and moving.)

I don't think this would make any difference.  Transfer mode
configuration is done using polling to work around problems like this
and because some controllers and devices raise IRQ too early.

-- 
tejun

      reply	other threads:[~2007-10-23  7:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-02 20:53 [patch 10/10] libata: fix (hopefully) all the remaining problems with devices failing setup/identify akpm
2007-10-03 20:44 ` Jeff Garzik
2007-10-23  7:35   ` Tejun Heo [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=471DA455.2030909@gmail.com \
    --to=htejun@gmail.com \
    --cc=akpm@linux-foundation.org \
    --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).