From: "Joseph P. Garcia" <jpgarcia@execpc.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: BMAC stuff - what I have
Date: Sun, 11 Feb 2001 00:13:34 -0600 [thread overview]
Message-ID: <20010211001334.54abdf4f.jpgarcia@execpc.com> (raw)
In-Reply-To: <20010211043822.8854.qmail@kunk.jriver.com>
On Sat, 10 Feb 2001 22:38:22 -0600 (CST), Robert E Brose II <bob@kunk.jriver.com> wrote:
> I see the same problem on my Rev C iMac at 100 mb in both 2.2 and 2.4
> kernels. I get slow transfers and broken scp's but not corrupted
> data on complete transfers. Same machine works fine in MacOS and OSX.
>
> Bob
Thanks for the input.
If it is true that the iMac has the same Tx problem, since they have always used BMAC+ (AppleSpec: 10/100 on all iMacs), I guess that this would mean that BMAC+ can also have this bug. Can any one confirm this with an additional case?
It seems rather erratic on which systems are afflicted. My brother's lombard is not affected, nor a wallstreet confirmed built after mine, which is.
In anycase, enough talk. Anyone know dbdma well enough to approach a fix? :)
--
Joseph P. Garcia
http://www.execpc.com/~jpgarcia
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-02-11 6:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 4:38 BMAC stuff - what I have Robert E Brose II
2001-02-11 6:13 ` Joseph P. Garcia [this message]
2001-02-11 7:47 ` Joseph P. Garcia
2001-02-11 18:09 ` BMAC stuff - update Joseph P. Garcia
2001-02-11 23:11 ` BMAC stuff - what I have Dan Malek
2001-02-12 8:44 ` Albrecht Dre_
-- strict thread matches above, loose matches on Subject: below --
2001-02-11 6:45 Iain Sandoe
[not found] <3A8579F6.4C5E97CD@vnet.ibm.com>
[not found] ` <Pine.LNX.4.21L.0102101430160.1671-100000@unix47.andrew.cmu.edu>
2001-02-10 21:01 ` Joseph P. Garcia
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=20010211001334.54abdf4f.jpgarcia@execpc.com \
--to=jpgarcia@execpc.com \
--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 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.