All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sebastian Piecha" <spi@gmxpro.de>
To: "Tomasz  B±tor" <tomba@bartek.tu.kielce.pl>,
	linux-kernel@vger.kernel.org
Subject: Re: What is the SiI 0680 chipset status?
Date: Wed, 03 Sep 2003 14:42:52 +0200	[thread overview]
Message-ID: <3F55FDEC.28048.34FF5921@localhost> (raw)
In-Reply-To: <20030902165537.GA1830@bartek.tu.kielce.pl>

> 
> Hi to all.
> I recently got MiNt PCI IDE ATA/133 RAID controller based on SiI 0680
> chipset. I browsed through the archives and I know that the driver is
> known to be broken and simply doesn't work.
> 
> That was some time ago, meanwhile there were some fixes/hdparm
> almost-solutions, but none of them seems to work. I remember that
> Andre Hendrick said he's talking with SiI guys to find a final
> solution, but no more info after that...
> 
> Therefore my question is: what is the current status of this driver?
> Are there any patches available? Or I will have to just buy another
> controller? (No problems with HPT or Promise?)
> 
I recently posted a problem with a Promise 
UltraTrak 133 TX2 controller (subject: PROBLEM: Powerquest Drive 
Image let the kernel panic). With kernel 2.4.20 every time moving 
several GB of data I get an OOPS. I already thought trying a 
controller with a SI680-chipset... Maybe that's not a good idea.

Mit freundlichen Gruessen/Best regards,
Sebastian Piecha

EMail: spi@gmxpro.de


      parent reply	other threads:[~2003-09-03 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02 16:55 What is the SiI 0680 chipset status? Tomasz  B±tor
2003-09-03 11:49 ` Alan Cox
2003-09-04  1:42   ` Tomasz  B±tor
2003-09-04 10:06     ` Alan Cox
2003-09-04 10:53       ` Tomasz  B±tor
2003-09-04  2:19   ` "bleating edge" " Resident Boxholder
2003-09-03 12:42 ` Sebastian Piecha [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=3F55FDEC.28048.34FF5921@localhost \
    --to=spi@gmxpro.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomba@bartek.tu.kielce.pl \
    /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.