linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Edward Falk <efalk@google.com>
To: Bryan O'Sullivan <bos@serpentine.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: Additions to libata patch archive
Date: Wed, 05 Oct 2005 10:47:01 -0700	[thread overview]
Message-ID: <43441195.1070707@google.com> (raw)
In-Reply-To: <1128488974.428.16.camel@camp4.serpentine.com>


> In case anyone should care, the original SiImage driver oopses during
> boot with recent kernels.
> 
> The reason I know this is that I just tried booting 2.6.14-rc3 with the
> 0.10 (SiImage) driver.  It appears to contain port multiplier support,
> which I need.  Tejun's rewrite doesn't, and SiImage wants me to sign an
> NDA to get a more recent driver of theirs that has port multiplier
> support.

The original vendor-supplied driver did not support port multipliers, 
but it had the hooks that implied they were thinking about it.  The 
original driver had a number of problems, mostly dealing with lack of 
error recovery as you have just discovered.

Tejun's driver is much better, and I have sent him some patches that 
will make it quite stable.


There are two approaches to port multiplier support -- one is to add it 
to the driver (a real kludge) or to add it to libata.  Kludging it into 
the driver is a quick-and-dirty solution, while adding it to libata will 
take more time.  I'm trying to find the time to do the latter.

	-ed falk

      reply	other threads:[~2005-10-05 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05  4:13 Additions to libata patch archive Jeff Garzik
2005-10-05  5:09 ` Bryan O'Sullivan
2005-10-05 17:47   ` Edward Falk [this message]

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=43441195.1070707@google.com \
    --to=efalk@google.com \
    --cc=bos@serpentine.com \
    --cc=bzolnier@gmail.com \
    --cc=jgarzik@pobox.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).