mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eyal Lebedinsky <eyal@eyal.emu.id.au>
To: Milan Kupcevic <milan@physics.harvard.edu>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	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: Sat, 25 Feb 2006 17:59:02 +1100	[thread overview]
Message-ID: <44000036.7070403@eyal.emu.id.au> (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

I totally agree with the fact that the Linux driver gets the ports wrong
when compared to the BIOS, Windows and surely contradicts the port
numbers printed on the board. I doubt we all got samples on the one
bad batch...

It *is* a real problem and if the solution is correct then I support it.

Maybe we need a quick feedback from current users: do you guys find
that the ports are detected as they are labelled (white silk screen)
on the board or do they show up out of order (as listed above by
Milan)?

-- 
Eyal Lebedinsky (eyal@eyal.emu.id.au) <http://samba.org/eyal/>
	attach .zip as .dat

  parent reply	other threads:[~2006-02-25  6:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25  1:09 Milan Kupcevic
2006-02-25  1:16 ` Jeff Garzik
2006-02-25  1:42   ` Milan Kupcevic
2006-02-25  6:59 ` Eyal Lebedinsky [this message]
2006-02-25 10:52   ` Christiaan den Besten
     [not found]     ` <442DB29D.1010102@avona.com>
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

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=44000036.7070403@eyal.emu.id.au \
    --to=eyal@eyal.emu.id.au \
    --cc=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

all inboxes | Powered by JetHome®