From: s-jaschke@t-online.de (Stefan Jaschke)
To: Francois Romieu <romieu@cogenit.fr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: epic100 error
Date: Fri, 20 Apr 2001 17:57:54 +0200 [thread overview]
Message-ID: <01042017575400.01716@antares> (raw)
In-Reply-To: <20010417184552.A6727@core.devicen.de> <01042016050400.01202@antares> <20010420163343.B4702@se1.cogenit.fr>
In-Reply-To: <20010420163343.B4702@se1.cogenit.fr>
On Friday 20 April 2001 16:33, Francois Romieu wrote:
> Stefan Jaschke <s-jaschke@t-online.de> ecrit :
> > I copied epic100.c from 2.4.2 into the 2.4.4-pre4 tree and it compiles
> > and works without problems.
> > This gives me a workable solution :-)
>
> Thanks for the info.
> Now, why do you get so much Receive Queue Empty indications...
Now, this is a question for more knowledgable persons than me :-)
Another question I have is about the different driver versions that
are around.
Till Harbaum <harbaum@telematik.informatik.uni-karlsruhe.de> just sent
me a driver which is directly from SMC:
> As i already mentioned in a posting, that for some reason didn't show up in
> the list, i got a driver module source directly from SMC, that works fine
> with 2.4.3 and has the ability to use the optical interface.
> Till
It unpacks to
18458 Jul 14 1999 copying
1931 Mar 9 09:30 debug.h
10451 Mar 12 13:39 list.h
123761 Mar 13 16:05 lm.c
11547 Mar 12 13:37 lm.h
14872 Apr 5 11:35 lm.o
4761 Apr 13 2000 lm_cfg.h
29169 Mar 13 16:05 lm_epic.h
335 Apr 5 17:14 makefile
22096 Mar 13 16:06 mm.c
4754 Mar 17 2000 mm.h
3672 Apr 5 11:35 mm.o
676 Mar 26 09:51 readme.txt
21874 Apr 5 11:35 smcpwr2.o
24572 Mar 13 16:14 um.c
3550 Mar 13 16:08 um.h
5628 Apr 5 11:34 um.o
and "copying" is the GPL. It seems to be a not yet released extension of the driver
available from http://www.smc.de/sites/support/download/PCI/9432/LINUX/src9432lu.zip.
Some changelog reads " 03/13/2001 Ling Yue for linux kernel 2.4".
Is there communication between SMC and your group?
--
Stefan R. Jaschke <stefan@jaschke-net.de>
http://www.jaschke-net.de
next prev parent reply other threads:[~2001-04-20 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 16:45 epic100 error Oliver Teuber
2001-04-17 20:34 ` Stefan Jaschke
[not found] ` <20010418204021.A14531@se1.cogenit.fr>
2001-04-20 8:22 ` Stefan Jaschke
2001-04-20 10:25 ` Francois Romieu
2001-04-20 11:30 ` Stefan Jaschke
2001-04-20 14:05 ` Stefan Jaschke
2001-04-20 14:33 ` Francois Romieu
2001-04-20 15:57 ` Stefan Jaschke [this message]
2001-04-20 16:45 ` Francois Romieu
2001-04-20 20:13 ` Stefan Jaschke
2001-04-20 11:09 ` Stefan Jaschke
2001-04-20 11:33 ` Jeff Garzik
2001-04-20 12:07 ` Stefan Jaschke
2001-04-20 8:14 ` Arnaldo Carvalho de Melo
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=01042017575400.01716@antares \
--to=s-jaschke@t-online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=romieu@cogenit.fr \
--cc=stefan@jaschke-net.de \
/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.