From: Erik Slagter <erik@slagter.name>
To: "Gaston, Jason D" <jason.d.gaston@intel.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@osdl.org>
Subject: RE: [PATCH] ich6m-pciid-piix.patch
Date: Sun, 03 Jul 2005 12:55:59 +0200 [thread overview]
Message-ID: <1120388159.4300.57.camel@localhost.localdomain> (raw)
In-Reply-To: <26CEE2C804D7BE47BC4686CDE863D0F5043A5782@orsmsx410>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On Sat, 2005-07-02 at 17:23 -0700, Gaston, Jason D wrote:
>>> Please do not apply this patch. The ICH6M SATA DID is all ready
>>> being used in the SATA ata_piix.c and ahci.c drivers. Adding the
>>> ICH6M SATA DID to the PATA piix.c driver will conflict. This patch
>>> would add the ICH6M >SATA controller DID 0x2653 to the PATA
>>> piix.c driver.
> > That's why you either enable piix support from the standard ide driver
> > xor from libsata. The comments in the configure script even mention this
> > fact!
> You need to have support for both at the same time if you want to run in
> enhanced mode and have full access to your PATA and SATA controllers and
> drives.
Hmmm. I guess this would be in the (imho unlikely) situation where you
have both PATA and SATA drives connected to the ICH6M.
I do see the problem, though. It's a "works for me(r)" solution ;-)
> I suggest you try to place your BIOS in Enhanced mode for the SATA/PATA
> controllers so that you have both the PATA and SATA DID's and
> controllers showing up. Then your PATA drive will show up as an IDE
> device and use the piix driver.
Bzzzt! Nice theory, but in practise, MANY bioses (including mine) don't
offer the choice to put the controller in whatever mode. Add to that,
that if you only have pata drives attached, it doesn't make much sense
to drive it with libata.
I'd be happy to drive my ICH6M with libata, but it just doesn't work
well. No smart&hdparm (the corresponding patch freezes the kernel every
now and then) support, drives show up as scsi drives..., no atapi
(unless #defined, but also not yet bugfree).
Well anyway, this is just my $0.02 I guess it won't make it into the
kernel, but you never know how might be able to use it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2005-07-03 10:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26CEE2C804D7BE47BC4686CDE863D0F5043A5782@orsmsx410>
2005-07-03 10:55 ` Erik Slagter [this message]
2005-07-02 18:44 Gaston, Jason D
2005-07-03 10:46 ` Erik Slagter
-- strict thread matches above, loose matches on Subject: below --
2005-07-02 10:57 Erik Slagter
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=1120388159.4300.57.camel@localhost.localdomain \
--to=erik@slagter.name \
--cc=akpm@osdl.org \
--cc=jason.d.gaston@intel.com \
--cc=linux-ide@vger.kernel.org \
--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
all inboxes | Powered by JetHome®