linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: "Jérôme VUARAND" <jerome.vuarand@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	Jerome Vuarand <jerome.vuarand@ubisoft.com>,
	linux-ide@vger.kernel.org
Subject: Re: Promise TX4 + SiI 3726 : only one disk visible
Date: Tue, 16 May 2006 09:18:05 +0900	[thread overview]
Message-ID: <44691A3D.4040804@gmail.com> (raw)
In-Reply-To: <89d273ba0605151712q7d6ab748q52ab321d45848a53@mail.gmail.com>

Jérôme VUARAND wrote:
> Thanks a lot for the quick answers. Sorry to have misread tejun's
> readme, I tought there was some abstraction layer between SATA
> protocol and SATAII extensions, so I didn't even suppose there could
> be a need for controller specific code to support port multiplier. I
> was clearly wrong.

Yeap, there is a layer, but it still needs low level support.

> So to be clear, there is not yet any support for my configuration
> (sata_promise+SiI3726) in any of your code branches ? If not which one
> should I start from to try to add the support myself (I never
> programmed anything in the kernel, so it would just be a newbie try) ?

No, not yet.  You can try but the biggest obstacle would be lack of 
document.  If you can access the doc, it shouldn't be too difficult, I 
guess.  You can analyze how sata_sil24 has been changed and update 
sata_promise similarly.

-- 
tejun

  parent reply	other threads:[~2006-05-16  0:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6EB652BF05BEE44FA2A29B23F3A71528045B3857@UBIMAIL1.ubisoft.org>
2006-05-15 23:24 ` Promise TX4 + SiI 3726 : only one disk visible Tejun Heo
2006-05-15 23:40   ` Jeff Garzik
2006-05-15 23:58     ` Jeff Garzik
     [not found]       ` <89d273ba0605151712q7d6ab748q52ab321d45848a53@mail.gmail.com>
2006-05-16  0:18         ` Tejun Heo [this message]
     [not found]           ` <89d273ba0605151924o5ce25807qe01ca3b9e2715b6@mail.gmail.com>
2006-05-16  2:27             ` Jeff Garzik
2006-05-16  2:34             ` 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=44691A3D.4040804@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=jerome.vuarand@gmail.com \
    --cc=jerome.vuarand@ubisoft.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 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).