From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
davej@redhat.com
Subject: Re: [PATCH] libata: fix broken Kconfig setup
Date: Mon, 17 Oct 2005 10:06:39 -0700 [thread overview]
Message-ID: <200510171006.39206.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <4353D96F.90805@pobox.com>
On Monday, October 17, 2005 10:03 am, Jeff Garzik wrote:
> Jesse Barnes wrote:
> > It does, since it prevents one of the ports from being bound by the
> > legacy IDE driver. But the whole thing is rather hackish to begin
> > with, and I prefer this hack to the existing code (in fact, Andrew
> > already queued up a patch from me in -mm that looks just like
> > yours).
> >
> > Ultimately, when libata gets ATAPI support, I think we just have to
> > declare libata and legacy IDE to be incompatible for combined mode
> > devices and remove the quirk. Then whichever driver loads first
> > will get the whole device, as it should.
>
> I would love to remove the quirk completely!
>
> Unfortunately combined mode is a runtime BIOS configuration, and there
> is also the lockup issue I mentioned in another email.
So sometimes the legacy IDE driver will lock up when it tries to drive
both ports in a combined configuration? In that case, can't we just
disable the legacy IDE driver for these chips and force the use of the
libata version?
Jesse
next prev parent reply other threads:[~2005-10-17 17:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 4:46 [PATCH] libata: fix broken Kconfig setup Jeff Garzik
2005-10-17 11:10 ` Matthias Urlichs
2005-10-17 11:20 ` Jeff Garzik
2005-10-17 15:14 ` Linus Torvalds
2005-10-17 15:32 ` Jeff Garzik
2005-10-17 15:58 ` Linus Torvalds
2005-10-17 16:21 ` Jeff Garzik
2005-10-17 16:38 ` Linus Torvalds
2005-10-17 16:53 ` Linus Torvalds
2005-10-17 17:11 ` Jeff Garzik
2005-10-17 17:25 ` Linus Torvalds
2005-10-17 17:38 ` Jeff Garzik
2005-10-19 11:49 ` Alistair John Strachan
2005-10-19 16:02 ` Randy.Dunlap
2005-10-17 17:01 ` Jeff Garzik
2005-10-18 11:15 ` Sergey Vlasov
2005-10-18 20:56 ` Jeff Garzik
2005-10-17 17:12 ` Linus Torvalds
2005-10-17 17:22 ` Jeff Garzik
2005-10-17 16:52 ` Jesse Barnes
2005-10-17 17:03 ` Jeff Garzik
2005-10-17 17:06 ` Jesse Barnes [this message]
2005-10-17 17:16 ` Jeff Garzik
2005-10-20 14:14 ` Alan Cox
2005-10-20 16:45 ` Jesse Barnes
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=200510171006.39206.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).