From: Wes Newell <w.newell@verizon.net>
To: "linux.ide" <linux-ide@vger.kernel.org>
Subject: Re: libata and PATA devices
Date: Thu, 11 Aug 2005 15:19:14 -0500 [thread overview]
Message-ID: <42FBB2C2.8060100@verizon.net> (raw)
In-Reply-To: <1123789132.4422.30.camel@localhost.localdomain>
On Thu, 2005-08-11 at 13:19 -0400, Jeff Garzik wrote:
>>Mark Lord wrote:
>>
>>
>>>Jeff Garzik wrote:
>>>
>>>
>>>>currently no one should be using libata for PATA support.
>>>>
>>>>
>>>We emailed back and forth extensively about how this has
>>>not been true since early this year. Modern laptops are
>>>using libata for the ICH6M support, simply because libata
>>>claims that chipset, and the IDE driver does not.
>>>These laptops are using PATA drives (eg. "FUJITSU MHV2100AH").
>>>
>>>
>>This sounds like a misconfigured kernel. The IDE driver should pick up
>>the PATA port, and libata should pick up the SATA port. Anything else
>>is a bug, and should be addressed by me or Bart.
>>
>>
While ya'll are talking about pata support, has anyone got a driver that
supports the pata ports of the SIS180 yet? And I don't care which
way.:-) As you might recall, I tried patching the 5513 driver, but had
limited success with constant lost interrupts. I'm not a C programmer
and don't know much about the whole IDE layout, but I'm willing to test
on a Jetway S755MAX Board, that constist of the standard pata ports off
the sis755 and a secondary SIS180 with 2 ports of sata and 1 channel
pata (2 drives). I'm running the 2.6.11 kernel, but can install whatever
you would want to test with on another drive.
next prev parent reply other threads:[~2005-08-11 20:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-07 17:48 libata and PATA devices Andreas Klöckner
2005-08-08 1:43 ` Tejun Heo
2005-08-08 3:02 ` Jeff Garzik
2005-08-08 10:10 ` Erik Slagter
2005-08-09 13:48 ` Mark Lord
2005-08-09 14:10 ` Mark Lord
2005-08-09 18:01 ` Jeff Garzik
2005-08-09 17:05 ` Erik Slagter
2005-08-09 18:02 ` Jeff Garzik
2005-08-09 17:59 ` Jeff Garzik
2005-08-11 3:57 ` Jeff Garzik
2005-08-11 9:37 ` Erik Slagter
2005-08-11 10:03 ` Bartlomiej Zolnierkiewicz
2005-08-11 10:17 ` Erik Slagter
2005-08-11 10:26 ` Bartlomiej Zolnierkiewicz
2005-08-11 15:29 ` Erik Slagter
2005-08-11 15:57 ` Bartlomiej Zolnierkiewicz
2005-08-11 16:48 ` Erik Slagter
2005-08-11 17:05 ` Mark Lord
2005-08-11 17:19 ` Jeff Garzik
2005-08-11 19:38 ` Erik Slagter
2005-08-11 20:19 ` Wes Newell [this message]
2005-08-11 20:21 ` Jeff Garzik
2005-08-11 20:25 ` Jeff Garzik
2005-08-13 11:30 ` Erik Slagter
2005-08-13 15:33 ` Jeff Garzik
2005-08-13 15:50 ` Erik Slagter
2005-08-13 15:56 ` Jeff Garzik
2005-08-13 16:03 ` Erik Slagter
2005-08-13 16:44 ` Jeff Garzik
2005-08-13 16:53 ` Erik Slagter
2005-08-15 21:39 ` Mark Lord
2005-08-16 7:21 ` Erik Slagter
2005-08-13 15:56 ` Tyler
2005-08-13 15:57 ` Jeff Garzik
2005-08-13 16:05 ` Erik Slagter
2005-08-13 16:42 ` Jeff Garzik
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=42FBB2C2.8060100@verizon.net \
--to=w.newell@verizon.net \
--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).