From: Jeff Garzik <jgarzik@pobox.com>
To: Milan Kupcevic <milan@physics.harvard.edu>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, trivial@rustcorp.com.au,
torvalds@osdl.org
Subject: Re: [PATCH] sata_promise: Port enumeration order - SATA 150 TX4, SATA 300 TX4
Date: Fri, 24 Feb 2006 20:16:57 -0500 [thread overview]
Message-ID: <43FFB009.6070403@pobox.com> (raw)
In-Reply-To: <43FFAE3D.7010002@physics.harvard.edu>
Milan Kupcevic wrote:
> From: Milan Kupcevic <milan@physics.harvard.edu>
>
> Fix Promise SATAII 150 TX4 (PDC40518) and Promise SATA 300 TX4
> (PDC40718-GP) wrong port enumeration order that makes it (nearly)
> impossible to deal with boot problems using two or more drives.
>
> Signed-off-by: Milan Kupcevic <milan@physics.harvard.edu>
> ---
>
> The current kernel driver assumes:
>
> port 1 - scsi3
> port 2 - scsi1
> port 3 - scsi0
> port 4 - scsi2
The current kernel driver assumes nothing, but simply exports what the
hardware gives us.
It sounds like you are trying to patch the kernel because you received
an incorrectly-wired board. NAK.
Jeff
next prev parent reply other threads:[~2006-02-25 1:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 1:09 [PATCH] sata_promise: Port enumeration order - SATA 150 TX4, SATA 300 TX4 Milan Kupcevic
2006-02-25 1:16 ` Jeff Garzik [this message]
2006-02-25 1:42 ` Milan Kupcevic
2006-02-25 6:59 ` Eyal Lebedinsky
2006-02-25 10:52 ` Christiaan den Besten
2006-03-31 22:52 ` Fabian Knittel
2006-05-30 21:31 ` Milan Kupcevic
2006-06-06 17:27 ` Fabian Knittel
2006-10-02 22:08 ` Evan Harris
2006-12-16 17:09 ` Jeff Garzik
2006-02-26 19:55 ` Oliver Joa
2006-02-26 19:56 ` Oliver Joa
-- strict thread matches above, loose matches on Subject: below --
2009-10-03 22:12 Walter Hutchins
2009-10-05 10:49 ` Mikael Pettersson
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=43FFB009.6070403@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=milan@physics.harvard.edu \
--cc=torvalds@osdl.org \
--cc=trivial@rustcorp.com.au \
/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).