From: Thomas Lau <lkthomas@hkicable.com>
To: Jocelyn Mayer <jocelyn.mayer@netgem.com>, linux-kernel@vger.kernel.org
Subject: Re: finding Tekram SCSI dc395U linux patch driver:
Date: Sat, 17 Feb 2001 00:06:23 +0800 [thread overview]
Message-ID: <3A8D4FFF.320E7A16@hkicable.com> (raw)
In-Reply-To: <3A8D2763.9080102@netgem.com>
Jocelyn Mayer wrote:
> >
> >
> > Well, I think it should add to normal kernel and do not need to patch,
> > Thanks
> >
> > also, why this driver still stick in ac3?
> > and where can I find the new version of this patch?
> > I think mandrake was improved that driver, Thanks
> >
> I'm not so sure...
> I've been using this driver for a long time,
> and there still are kernel Ooops and hangs
> with the 1.32 driver...
> Actually, it's quite stable, but only with 5 M
> speed. It's a pity when your card can drive
> a SCSI bus up to 40 M/s....
> But, even with that speed, I got problems
> from time to time....
>
> So, you should take a good care of what you do...
> But, maybe it shold be integrated into the kernel
> so a lot of people could test and (maybe) debut it...
>
> Jocelyn Mayer.
>
> >
that's what I want to do, if not included in kernel = not a lot of people
know what is this, so no one will help to improve this driver!
I hope alan can help to add this driver into kernel hacks, Thanks
next prev parent reply other threads:[~2001-02-16 16:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-16 13:13 finding Tekram SCSI dc395U linux patch driver: Jocelyn Mayer
2001-02-16 16:06 ` Thomas Lau [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-21 3:00 James Cleverdon
2001-02-15 20:35 Thomas Lau
2001-02-15 21:46 ` Juergen Schoew
2001-02-16 9:01 ` Chmouel Boudjnah
2001-02-16 10:27 ` Thomas Lau
2001-02-20 16:27 ` Kurt Garloff
2001-02-20 17:00 ` Thomas Lau
2001-02-20 2:41 ` Tim Wright
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=3A8D4FFF.320E7A16@hkicable.com \
--to=lkthomas@hkicable.com \
--cc=jocelyn.mayer@netgem.com \
--cc=linux-kernel@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