From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Fix silly thinko in sungem network driver.
Date: Sat, 21 Feb 2004 11:24:50 +1100 [thread overview]
Message-ID: <1077323090.10877.9.camel@gaston> (raw)
In-Reply-To: <20040220162318.097006ee.davem@redhat.com>
On Sat, 2004-02-21 at 11:23, David S. Miller wrote:
> I thought the idea was that if IBURST doesn't stick, then the Apple specific
> bits aren't implemented?
>
> That's what the comment says.
I though the IBURST that doesn't stick was specific to latest Apple versions ?
Those latest Apple versions are _also_ the ones implementing the magic bug
fix bits (those appeared with the G5).
Or did I get it backward ? Hrm, maybe I did... Here's Apple code:
fConfiguration = kConfiguration_TX_DMA_Limit // default Configuration value
| kConfiguration_RX_DMA_Limit
| kConfiguration_Infinite_Burst
| kConfiguration_RonPaulBit
| kConfiguration_EnableBug2Fix;
WRITE_REGISTER( Configuration, fConfiguration ); // try the default
ui32 = READ_REGISTER( Configuration ); // read it back
if ( (ui32 & kConfiguration_Infinite_Burst) == 0 )
{ // not infinite-burst capable:
ELG( 0, 0, 'Lims', "UniNEnet::initChip: set TX_DMA_Limit and RX_DMA_Limit." );
fConfiguration = (0x02 << 1) | (0x08 << 6); // change TX_DMA_Limit, RX_DMA_Limit
WRITE_REGISTER( Configuration, fConfiguration );
}
What does your doco says ?
Ben.
next prev parent reply other threads:[~2004-02-21 0:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200402202307.i1KN7GBR003938@hera.kernel.org>
2004-02-21 0:04 ` Fix silly thinko in sungem network driver Benjamin Herrenschmidt
2004-02-21 0:12 ` Benjamin Herrenschmidt
2004-02-21 0:19 ` Benjamin Herrenschmidt
2004-02-21 0:23 ` David S. Miller
2004-02-21 0:24 ` Benjamin Herrenschmidt [this message]
2004-02-21 0:32 ` Benjamin Herrenschmidt
2004-02-21 0:34 ` David S. Miller
2004-02-21 0:35 ` Benjamin Herrenschmidt
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=1077323090.10877.9.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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