9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] PCMCIA Ethernet
Date: Thu, 18 Sep 2008 14:41:32 +0000	[thread overview]
Message-ID: <091820081441.11092.48D2689C000B704300002B5422218683269B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <d3bdd35412e9fc3183c3e1a269addd1b@quintile.net>

> I was using a 3c589 until a few years ago, then  I moved to
> a Netgear FA411 which is somwhat more mechanically robust -
> I broke the plug on the 3com card :-(

It sounds like for a number of people it's working just
fine, and no one's put forward any real magic to make
it work, except for using the other slot on some machines.
So that brings up the question, why is it working on
some machines, and some slots, and not others.  To
me that seems to point to the PCMCIA code, but then
aux/pcmcia picks it up.  I expect I'll try to move
forward by adding some debug output to try and trace
what's happening and what's not.  But if anyone
has any great PCMCIA wisdom, feel free to speak
up :-)  Along those lines, if a CardBus controller
is not recognized by devpccard, should I expect
dev82365 to handle it correctly?

And I too have had trouble with the connectors on
the 3com cards.  This one will end up in a rack,
so I figure it's a good place for a pigtail that
can't take too much stress.

Thanks,
BLS




  reply	other threads:[~2008-09-18 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17  2:51 Brian L. Stuart
2008-09-17  8:55 ` Martin Neubauer
2008-09-17 14:29   ` Brian L. Stuart
2008-09-17 21:31     ` Steve Simon
2008-09-18 14:41       ` Brian L. Stuart [this message]
2008-09-17 20:28 ` Andy Spencer
2008-09-18 14:23   ` Brian L. Stuart

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=091820081441.11092.48D2689C000B704300002B5422218683269B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
    --to=blstuart@bellsouth.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).