linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Moritz Rigler <moritz1234567@gmx.de>, linux-ide@vger.kernel.org
Subject: Re: [PATCH #upstream-fixes] libata: implement and use HORKAGE_NOSETXFER
Date: Thu, 15 Jan 2009 19:06:29 +0900	[thread overview]
Message-ID: <496F0AA5.1000908@kernel.org> (raw)
In-Reply-To: <20090115094500.18d60455@lxorguk.ukuu.org.uk>

Alan Cox wrote:
>>> Yes - I'd like it to just work, but I'd like it to just work without
>>> breaking anything else, without adding device specific special cases and
>>> ideally in a way that makes other stuff that is similarly odd just work
>>> too.
>> Then, how do you suggest proceeding on it?  Without a bus tracer, we
>> can't easily tell what Windows is doing and on native SATA skipping
>> SETXFER isn't likely to cause any serious problem.  It's basically
>> noop.
> 
> I would suggest we issue the SETXFER always. If it times out then we will
> revalidate the identify data so we can use that to see what mode we are
> actually in.

Hmmm... our current timeout for SETXFER is 5s, so it wouldn't be nice
but not too bad either.  Alright, I'll brew up something.

-- 
tejun

  reply	other threads:[~2009-01-15 10:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 14:15 [PATCH #upstream-fixes] libata: implement and use HORKAGE_NOSETXFER Moritz Rigler
2009-01-07 14:23 ` Alan Cox
2009-01-09  0:11   ` Robert Hancock
2009-01-15  5:48   ` Tejun Heo
2009-01-15  9:45     ` Alan Cox
2009-01-15 10:06       ` Tejun Heo [this message]
2009-01-15 13:48         ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07 14:18 Moritz Rigler
2008-12-21 21:18 PIONEER DVD-RW DVRTD08 is disabled if there is no disc present at boot time linux-ide
2008-12-22  0:22 ` Robert Hancock
2008-12-22 10:02   ` Tejun Heo
2008-12-22 12:13     ` linux-ide
2008-12-23  3:03       ` Tejun Heo
2008-12-24 13:40         ` linux-ide
2008-12-29  8:14           ` Tejun Heo
2008-12-29 21:32             ` linux-ide
2009-01-06 22:51               ` linux-ide
2009-01-07  2:01                 ` [PATCH #upstream-fixes] libata: implement and use HORKAGE_NOSETXFER Tejun Heo
2009-01-07  9:40                   ` Alan Cox
2009-01-07 10:27                     ` Tejun Heo
2009-01-07 10:53                       ` Alan Cox
2009-01-07 11:04                         ` Tejun Heo
2009-05-25  3:10                           ` Tejun Heo
2009-05-25  8:11                             ` Alan Cox
2009-07-08  8:00                               ` Tejun Heo
2009-07-08 10:14                                 ` Alan Cox
2009-07-08 11:16                                   ` Tejun Heo
2009-07-08 12:21                                     ` Alan Cox
2009-07-08 23:07                                       ` Tejun Heo
2009-07-08 14:53                                   ` Sergei Shtylyov
2009-07-08 15:06                                     ` 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=496F0AA5.1000908@kernel.org \
    --to=tj@kernel.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@vger.kernel.org \
    --cc=moritz1234567@gmx.de \
    /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).