From: walt <wa1ter@myrealbox.com>
To: linux-kernel@vger.kernel.org
Subject: More on Broadcom gigbit for Jeff
Date: Mon, 01 Sep 2003 07:17:50 -0700 [thread overview]
Message-ID: <3F53550E.8030708@myrealbox.com> (raw)
Hi Jeff,
I've narrowed down the source of my Broadcom problem to the 'tg3.c + tg3.h'
portions of this patch:
ftp://ftp.kernel.org/pub/linux/kernel/v2.4/testing/incr/patch-2.4.21-pre4-pre5.gz
That is, if I build a 2.4.21-pre4 kernel it works normally -- but if I then apply
just the tg3.c parts of the above patch I get my usual bug.
(If you'll recall, I'm the one who needs to do an ifconfig down/up cycle on my
ASUS A7V8X mobo with the built-in tg3 chip before it will start transmitting
packets.)
Unfortunately this patch has many changes that I don't understand well enough so
that I can cull them out and apply them individually.
Is it reasonable to try to do break this patch down into pieces? It all looks
like one big update to me.
Any other debugging ideas?
Thanks.
reply other threads:[~2003-09-01 21:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3F53550E.8030708@myrealbox.com \
--to=wa1ter@myrealbox.com \
--cc=linux-kernel@vger.kernel.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