linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joseph Garcia <jpgarcia@execpc.com>
To: Josh Huber <huberj@wpi.edu>
Cc: Linux/PowerPC Devel List <linuxppc-dev@lists.linuxppc.org>
Subject: Re: BMAC eth problems...
Date: Tue, 08 Feb 2000 07:22:45 -0600	[thread overview]
Message-ID: <38A018A5.FD10C45D@execpc.com> (raw)
In-Reply-To: 20000208020802.B5287@majere.nightshade.org


Josh Huber wrote:
> Anyone else seeing this?

My wallstreet/300 has a similar, possibly related problem.  any FTP transfer
originating from my powerbook in Linux (under any client or server) has a max
transfer under 100k.  This is a BMAC driver problem.  my brother's lombard
(BMAC+) seems to have no problem.  The big thing to notice is that in my case,
the traffic is colliding... with itself.  Duplex problem? (BMAC+ can, BMAC
cant).. but since we're not on a switched hub, that doesn't make much sense.

MacOS has no problems with my ethernet card; incoming FTP transfers work normal;
and i double checked with an FTP to myself (using lo), and it went fast.  So i
deduce this is a problem in someway connected to the hardware driver.

I have tested one theory.  In bmac.c, there is a delay called MIFDELAY that in
2.2.1 was 500, and now is 10.  I tried putting it back to make sure it wasn't
tripping on itself with that, but there was no improvement.

Other ideas?

--
Joseph P. Garcia      jpgarcia@execpc.com      jpgarcia@lidar.ssec.wisc.edu
CS Undergraduate                      Student Employee - Systems Programmer
University of Wisconsin - Madison                            UW Lidar Group

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

       reply	other threads:[~2000-02-08 13:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20000208020802.B5287@majere.nightshade.org>
2000-02-08 13:22 ` Joseph Garcia [this message]
2000-02-08 20:06   ` BMAC eth problems Wolfgang Denk

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=38A018A5.FD10C45D@execpc.com \
    --to=jpgarcia@execpc.com \
    --cc=huberj@wpi.edu \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).