All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Fowler <cfowler@outpostsentinel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Bob Tracy <rct@gherkin.frus.com>,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: [BUG] dm9601 driver won't init device properly
Date: Sat, 24 Jul 2010 10:54:02 -0400	[thread overview]
Message-ID: <1279983242.11931.4.camel@cfowler-desktop> (raw)
In-Reply-To: <93420.1279982681@localhost>

On Sat, 2010-07-24 at 10:44 -0400, Valdis.Kletnieks@vt.edu wrote:
> Wow. An "ethernet" card that won't do an MTU of 1500 even under
> Windows.  May I
> add this to my gallery of examples I use when people say "no vendor
> could
> *possibly* ship hardware that fscked up"? :) 

A lot of these "cards" are not meant for you and I.  They are meant for
casual desktop users that would never put any amount of load on them.

About 6 years ago we needed some PCMCIA modem cards and bought 100 of
them from a vendor for $25/ea.  They started failing in the field.  When
calling they just could not sync up.  Only a reboot could fix the
problem.  What we learned was that a combination of heat and other
factors caused them to drift so much the timing was off.  We replaced
those in the field with Zoom 3075 at about $65/ea.  These modems were
not meant for our solution.  They were meant for casual laptop users
that needed to dial an ISP every so often.  I was expecting them to work
in a box that would stay up 24x7.  They couldn't handle it.  I wrote a
perl program that used a TLS-4 simulator and would dial the modem
constantly.  The failures were too much.  On the Zooms we would average
10 failures per 1000 calls.






  reply	other threads:[~2010-07-24 15:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-23 19:57 [BUG] dm9601 driver won't init device properly Bob Tracy
2010-07-23 20:19 ` Bob Tracy
2010-07-24 14:44 ` Valdis.Kletnieks
2010-07-24 14:54   ` Chris Fowler [this message]
2010-07-24 16:43   ` Bob Tracy

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=1279983242.11931.4.camel@cfowler-desktop \
    --to=cfowler@outpostsentinel.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=rct@gherkin.frus.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 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.