From: Jeff Garzik <jgarzik@pobox.com>
To: Evan Harris <eharris@puremagic.com>
Cc: Milan Kupcevic <milan@physics.harvard.edu>,
Fabian Knittel <fabian.knittel@avona.com>,
linux-scsi@vger.kernel.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Eyal Lebedinsky <eyal@eyal.emu.id.au>,
Stan Seibert <volsung@mailsnare.net>,
linux-ide@vger.kernel.org,
Christiaan den Besten <chris@scorpion.nl>,
Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: [PATCH] sata_promise: Port enumeration order - SATA 150 TX4, SATA 300 TX4
Date: Sat, 16 Dec 2006 12:09:00 -0500 [thread overview]
Message-ID: <4584282C.5060803@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0610021700350.10249@kinison.puremagic.com>
Evan Harris wrote:
>
> I have a card that mirrors this one from your list:
>
> Retail name: SATA300 TX4
> Chip label: PDC40718-GP SATAII300
> Vendor-Device number: 105a:3d17 (rev 02)
>
> Through testing, I've found linux 2.6.16 and 2.6.17 find the ports in
> this order (the list is ordered by linux detection):
>
> 1. silkscreen port 3
> 2. silkscreen port 2
> 3. silkscreen port 4
> 4. silkscreen port 1
>> NOTE: the patch I have submitted (
>> http://marc.theaimsgroup.com/?l=linux-ide&m=114082978311290&w=2 ) is a
>> solution that doesn't know about the older Promise SATA controllers,
>> which are not affected with the "new wiring" problem, so the older
>> controllers will appear screwed if you use it.
>>
>> Hopefully we will collect enough info about all the SATA Promise
>> controllers to distinguish the new and the old wiring controllers,
>> then produce a new patch that will be a correct solution to the "new
>> wiring" problem.
Mikael Pettersson has been doing some excellent work recently on
sata_promise. If enough data has been collected on this sata_promise
port enumeration problem, maybe the data could be collated and proposed
via Mikael as a patch?
Jeff
next prev parent reply other threads:[~2006-12-16 17:09 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
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 [this message]
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=4584282C.5060803@pobox.com \
--to=jgarzik@pobox.com \
--cc=chris@scorpion.nl \
--cc=eharris@puremagic.com \
--cc=eyal@eyal.emu.id.au \
--cc=fabian.knittel@avona.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=milan@physics.harvard.edu \
--cc=volsung@mailsnare.net \
/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).