From: Jeff Garzik <jgarzik@pobox.com>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>
Cc: linux-ide@vger.kernel.org
Subject: Re: Promise SATAII150 TX4: strange disk ordering
Date: Tue, 30 Aug 2005 00:44:35 -0400 [thread overview]
Message-ID: <4313E433.1080602@pobox.com> (raw)
In-Reply-To: <430E4AB0.2060600@eyal.emu.id.au>
Eyal Lebedinsky wrote:
> I needed a 4-port SATA controller and this was was picked. It seems
> to work OK, however I find that Linux (2.6.12.5 and .13-rc7) see
> the disks in a different order than the labelled sockets (which do
> match what the BIOS detection lists at bootup).
>
> It is not even the reverse order:
> TX4 socket sata_promise ata*
> 1 4
> 2 2
> 3 1
> 4 3
> This order looks stable - I connected a different number of disks
> on some ports and this ordering was maintained.
sata_promise driver just presents the devices in the order that the
board maker has wired each port to the chip. What may be labelled "port
3" on the board might be wired to the chip's port-0. sata_promise just
presents what it is given.
Jeff
next prev parent reply other threads:[~2005-08-30 4:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 22:48 Promise SATAII150 TX4: strange disk ordering Eyal Lebedinsky
2005-08-30 4:44 ` Jeff Garzik [this message]
2005-08-30 10:31 ` Eyal Lebedinsky
2005-09-10 1:29 ` Promise SATAII150 TX4 or raidreconf broken Eyal Lebedinsky
2005-09-10 15:02 ` Thorild Selen
2005-09-11 2:38 ` Eyal Lebedinsky
2005-09-11 15:50 ` Eyal Lebedinsky
2005-09-12 22:50 ` Promise SATAII150 TX4 or raidreconf broken - answer Eyal Lebedinsky
2005-09-18 8:56 ` Tyler
2005-09-18 12:03 ` Promise SATAII150 TX4 ide errors Eyal Lebedinsky
-- strict thread matches above, loose matches on Subject: below --
2005-08-26 3:05 Promise SATAII150 TX4: strange disk ordering Allen Bolderoff
2005-08-26 8:46 ` Erik Slagter
2005-08-31 1:40 ` Thorild Selen
2005-08-31 14:15 ` Brad Campbell
2005-08-31 14:33 ` Thorild Selen
2005-08-31 14:50 ` Brad Campbell
2005-08-31 14:59 ` Ian Oliver
2005-08-31 18:31 ` Tyler
2005-09-01 12:53 ` Ian Oliver
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=4313E433.1080602@pobox.com \
--to=jgarzik@pobox.com \
--cc=eyal@eyal.emu.id.au \
--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).