From: Bill Fink <billfink@mindspring•com>
To: Anton Blanchard <anton@samba•org>
Cc: linuxppc-dev@lists•linuxppc.org, jes@trained-monkey•org,
Bill Fink <billfink@mindspring•com>
Subject: Re: 2.4.19-pre8-ben0 acenic driver and 867 MHz G4 sound problems
Date: Thu, 9 May 2002 11:30:45 -0400 [thread overview]
Message-ID: <20020509113045.35ae8de5.billfink@mindspring.com> (raw)
In-Reply-To: <20020509145005.GP10468@krispykreme>
Yep, that fixed it!!! Thanks a bunch.
-Bill
On Fri, 10 May 2002, Anton Blanchard wrote:
> > Unfortunately, I now have
> > a new problem as the acenic driver is now broken (using a NetGear GA620
> > NIC). The previously working version was from a 2.4.17-pre2-ben0 kernel.
> > I can send a diff between the two sources if that would be of any help.
>
> Does this patch help?
>
> Jes could you please send this patch on to Marcelo/Linus, they want your
> OK before taking it.
>
> Anton
>
> diff -urN linux-2.5/drivers/net/acenic.c linux-2.5_work/drivers/net/acenic.c
> --- linux-2.5/drivers/net/acenic.c Thu Apr 4 23:19:50 2002
> +++ linux-2.5_work/drivers/net/acenic.c Tue Apr 9 14:44:56 2002
> @@ -2692,7 +2692,7 @@
> flagsize &= ~BD_FLG_COAL_NOW;
> #endif
>
> - if (!ACE_IS_TIGON_I(ap)) {
> + if (ACE_IS_TIGON_I(ap)) {
> writel(addr >> 32, &desc->addr.addrhi);
> writel(addr & 0xffffffff, &desc->addr.addrlo);
> writel(flagsize, &desc->flagsize);
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-09 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-09 14:37 2.4.19-pre8-ben0 acenic driver and 867 MHz G4 sound problems Bill Fink
2002-05-09 13:00 ` Benjamin Herrenschmidt
[not found] ` <20020509122340.72cf75bd.billfink@mindspring.com>
2002-05-10 3:52 ` Bill Fink
2002-05-09 14:50 ` Anton Blanchard
2002-05-09 14:55 ` Jes Sorensen
2002-05-09 15:30 ` Bill Fink [this message]
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=20020509113045.35ae8de5.billfink@mindspring.com \
--to=billfink@mindspring$(echo .)com \
--cc=anton@samba$(echo .)org \
--cc=jes@trained-monkey$(echo .)org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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