From: Mark Lord <liml@rtr.ca>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <tj@kernel.org>, Robert Hancock <hancockr@shaw.ca>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: 2.6.27.6 question: ata_sff_hsm_move: ata15 (why always ata15)?
Date: Tue, 25 Nov 2008 11:35:02 -0500 [thread overview]
Message-ID: <492C2936.9080608@rtr.ca> (raw)
In-Reply-To: <20081124183204.2d3734e3@lxorguk.ukuu.org.uk>
Alan Cox wrote:
>> Well ata_piix for starters. Verified here by me.
>
> Some piix are fine (mine are) so maybe its a device property in part.
> Certainly it is needed for some combinations including current stuff like
> jmicron PATA ports.
..
Agreed -- here it was a notebook (Dell Inspiron 9300) with ata_piix
and a PATA drive. So the mainboard in the notebook had an onboard bridge
chip to adapt the PATA drive to the internal SATA port.
The subsequent model notebook (Dell Inspiron 9400) has very similar innards,
except it now uses SATA drives, so no bridge chip.
The former needs DRQ draining, the latter does not.
So, yeah, it's probably the bridge chip in this case.
Cheers
next prev parent reply other threads:[~2008-11-25 16:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 23:55 2.6.27.6 question: ata_sff_hsm_move: ata15 (why always ata15)? Justin Piszcz
2008-11-15 0:12 ` Justin Piszcz
2008-11-15 3:22 ` Robert Hancock
2008-11-15 10:34 ` Alan Cox
2008-11-16 6:14 ` Tejun Heo
2008-11-16 9:11 ` Justin Piszcz
2008-11-16 9:14 ` Tejun Heo
2008-11-16 11:25 ` Alan Cox
2008-11-24 18:20 ` Mark Lord
2008-11-24 18:32 ` Alan Cox
2008-11-25 16:35 ` Mark Lord [this message]
2008-11-15 17:39 ` Mario 'BitKoenig' Holbe
2008-11-15 22:00 ` Justin Piszcz
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=492C2936.9080608@rtr.ca \
--to=liml@rtr.ca \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hancockr@shaw.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=tj@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).