From: Robert PipCA <robertpipca@yahoo.com>
To: vortex@scyld.com
Cc: linux-kernel@vger.kernel.org
Subject: MTU discovery
Date: Mon, 10 Jun 2002 00:45:07 -0700 (PDT) [thread overview]
Message-ID: <20020610074507.69402.qmail@web21301.mail.yahoo.com> (raw)
Hi,
I'm working on a project that require knowing the
max MTU size supported by the 3Com PCI 3c905C
(Boomerang).
The datasheet provided by 3Com does not mention it,
and I already did the usual google search, but didn't
find it neither.
Does anyone knows a "generic way" of knowing this
(or chip-specific)?
Thanks in advance.
--Robert
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
next reply other threads:[~2002-06-10 7:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-10 7:45 Robert PipCA [this message]
2002-06-10 8:05 ` MTU discovery Matti Aarnio
2002-06-10 8:23 ` Robert PipCA
2002-06-10 9:50 ` Olivier Galibert
2002-06-10 21:45 ` Bill Davidsen
2002-06-10 22:02 ` Joel Jaeggli
2002-06-11 3:31 ` BALBIR SINGH
2002-06-11 3:46 ` Joel Jaeggli
2002-06-11 19:27 ` [vortex] " Donald Becker
2002-06-12 0:57 ` Jeff Garzik
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=20020610074507.69402.qmail@web21301.mail.yahoo.com \
--to=robertpipca@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vortex@scyld.com \
/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