From: Thomas Lau <lkthomas@hkicable.com>
To: Chmouel Boudjnah <chmouel@mandrakesoft.com>,
linux-kernel@vger.kernel.org
Subject: Re: finding Tekram SCSI dc395U linux patch driver:
Date: Fri, 16 Feb 2001 18:27:20 +0800 [thread overview]
Message-ID: <3A8D0088.2E147087@hkicable.com> (raw)
In-Reply-To: <XFMail.010215224622.Juergen.Schoew@unix-ag.org> <m3d7cj0zok.fsf@giants.mandrakesoft.com>
Chmouel Boudjnah wrote:
> Juergen Schoew <Juergen.Schoew@unix-ag.uni-siegen.de> writes:
>
> > Hi,
> > On 15-Feb-01 Thomas Lau wrote:
> > > hey, I found this driver on mandrake kernel sources, it's ac3, but I
> > > need ac14 code, also, why still not port this driver into kernel?
> > > the patch file already released 1 years ago
> >
> > Have you checked http://www.garloff.de/kurt/linux/dc395/index.html
> > there ist a driver Version 1.32 (2000-12-02).
>
> it's the version included with the mandrake kernel.
>
> --
> MandrakeSoft Inc http://www.chmouel.org
> --Chmouel
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
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
next prev parent reply other threads:[~2001-02-16 10:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 20:35 finding Tekram SCSI dc395U linux patch driver: Thomas Lau
2001-02-15 21:46 ` Juergen Schoew
2001-02-16 9:01 ` Chmouel Boudjnah
2001-02-16 10:27 ` Thomas Lau [this message]
2001-02-20 16:27 ` Kurt Garloff
2001-02-20 17:00 ` Thomas Lau
2001-02-20 2:41 ` Tim Wright
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 13:13 Jocelyn Mayer
2001-02-16 16:06 ` Thomas Lau
2001-02-21 3:00 James Cleverdon
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=3A8D0088.2E147087@hkicable.com \
--to=lkthomas@hkicable.com \
--cc=chmouel@mandrakesoft.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 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.