All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Skotte <sfs@enhance-it.dk>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: State of Port Multiplier Support in libata?
Date: Mon, 02 Jul 2007 09:37:53 +0200	[thread overview]
Message-ID: <4688AB51.8080801@enhance-it.dk> (raw)
In-Reply-To: <4688A74B.7000604@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tejun Heo wrote:
> Stefan Skotte wrote:
>> Hi,
>>
>> I was wondering what the odds are that my setup could be supported:
>>
>> * Stardom/Raidon SOHOTANK ST-6600 (5 disk SATA array)
>> (http://www.stardom.com.tw/sohotank%20st6600.htm)
>> * STLab Silicon Image 3531 NCQ/FIS PMP PCIe adapter with one eSATA port
>> (uses sata_sil24).
>> (http://www.st-lab.com/assign.asp?keyid=bf9)
>>
>> The classical example of it not working properly is that only one disk
>> in bay 2 is recognized; all other does not respond at all:
> 
> Get 2.6.22-rc6 and apply patches from the following page.
> 
>   http://home-tj.org/wiki/index.php/Libata-tj-stable
> 
> It should work.
> 

Thanks alot :) - I'm actually building it now on 2.6.22-rc6.

However there seems to be something within ipr.c that doesn't compile right:

==========================================================
Error Msg:
==========================================================
drivers/scsi/ipr.c: In function ‘__ipr_eh_dev_reset’:
drivers/scsi/ipr.c:3955: warning: passing argument 4 of ‘ata_do_eh’ from
incompatible pointer type
drivers/scsi/ipr.c: In function ‘ipr_ata_phy_reset’:
drivers/scsi/ipr.c:5049: error: ‘struct ata_port’ has no member named
‘device’
drivers/scsi/ipr.c:5053: error: ‘struct ata_port’ has no member named
‘device’
drivers/scsi/ipr.c:5056: error: ‘struct ata_port’ has no member named
‘device’
make[3]: *** [drivers/scsi/ipr.o] Error 1
make[2]: *** [drivers/scsi] Error 2
make[1]: *** [drivers] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.22-rc6'
make: *** [debian/stamp-build-kernel] Error 2
==========================================================

I just removed the ipr module since I'm not going to use it, but maybe
I'm doing something wrong since I'm usng the debian build process (?),
anyways I downloaded 2.6.22-rc6 from testing on kernel.org, so that
should atleast be right.

Thanks for getting back to me, I will report back how well my 3531-based
controller fares...

Kind regards,
Stefan


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGiKs/+vG8YFo3LPMRAjVVAJ9Zg1mKZh5UKuRzcm/8pB1Oh4tAfQCdGV5R
Ejekf0OS2bfmf0UqGnp7jAY=
=Zg0T
-----END PGP SIGNATURE-----

  reply	other threads:[~2007-07-02  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29  9:47 State of Port Multiplier Support in libata? Stefan Skotte
2007-07-02  7:20 ` Tejun Heo
2007-07-02  7:37   ` Stefan Skotte [this message]
2007-07-02  7:51     ` Tejun Heo
2007-07-02  9:21       ` Stefan Skotte
2007-07-02  9:36         ` Tejun Heo
2007-07-02 13:24           ` Stefan Skotte
2007-07-02 15:07             ` Tejun Heo
2007-07-02 21:03               ` Stefan Skotte
2007-07-03  3:06                 ` Tejun Heo
2007-07-08 18:57                   ` Stefan Skotte
2007-07-09  1:42                     ` Tejun Heo

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=4688AB51.8080801@enhance-it.dk \
    --to=sfs@enhance-it.dk \
    --cc=htejun@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.