From: Michael Rozhavsky <mrozhavsky@opticalaccess.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel EEPro 100 with kernel drivers
Date: Mon, 29 Oct 2001 13:45:00 +0200 [thread overview]
Message-ID: <20011029134500.K24143@opticalaccess.com> (raw)
In-Reply-To: <20011029134000.J24143@opticalaccess.com> <E15yAuo-0002Se-00@the-village.bc.nu>
In-Reply-To: <E15yAuo-0002Se-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Oct 29, 2001 at 11:49:14AM +0000
On Mon, Oct 29, 2001 at 11:49:14AM +0000, Alan Cox wrote:
> > We have exactly the same problem with 2.4.9, 2.4.10 and 2.4.13, so
> > We had to switch to Intel's driver.
>
> 10Mbit half duplex ?
10Mbit but Full duplex.
Best regards.
--
Michael Rozhavsky Tel: +972-4-9936248
mrozhavsky@opticalaccess.com Fax: +972-4-9890564
Optical Access
Senior Software Engineer www.opticalaccess.com
next prev parent reply other threads:[~2001-10-29 11:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 1:13 Intel EEPro 100 with kernel drivers Thomas Langås
2001-10-29 1:57 ` Jim Hull
2001-10-29 3:43 ` J Sloan
2001-10-31 8:01 ` Thomas Langås
2001-10-31 15:22 ` Andrey Savochkin
2001-10-31 15:52 ` Kirill Ratkin
2001-11-01 7:55 ` Thomas Langås
2001-11-01 9:47 ` Andrey Savochkin
2001-11-01 10:00 ` Thomas Langås
2001-10-31 18:10 ` Juergen Hasch
2001-11-01 8:03 ` Thomas Langås
2001-11-01 8:48 ` Juergen Hasch
2001-11-01 9:06 ` Thomas Langås
2001-11-01 9:43 ` Juergen Hasch
2001-11-01 11:11 ` Andrey Savochkin
2001-11-01 12:00 ` Thomas Langås
2001-11-01 12:15 ` Juergen Hasch
2001-11-01 13:39 ` Henning P. Schmiedehausen
2001-10-29 10:44 ` Alan Cox
2001-10-29 11:40 ` Michael Rozhavsky
2001-10-29 11:49 ` Alan Cox
2001-10-29 11:45 ` Michael Rozhavsky [this message]
2001-10-29 13:52 ` Thomas Langås
2001-10-30 8:36 ` Jarmo Järvenpää
2001-10-30 8:54 ` Dead2
2001-10-30 9:02 ` Jarmo Järvenpää
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=20011029134500.K24143@opticalaccess.com \
--to=mrozhavsky@opticalaccess.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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