From: Dean Matsen <deanmatsen@earthlink.net>
To: linuxppc-embedded@lists.linuxppc.org
Subject: [PATCH] Solves problems when PHY has no interrupts
Date: Tue, 08 Jul 2003 21:06:10 -0700 [thread overview]
Message-ID: <3F0B94B2.5090607@earthlink.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
Hello all,
the enclosed patch applies to the Monta Vista 2.4.22-pre3 kernel
or thereabouts.
Our PPC implementations have no PHY IRQ support. I notice that
the file arch/ppc/8xx_io/fec.c now has a variable HAVE_PHY_INTERRUPT,
which is something like what I originally did. But, I had to
make another change as well.
Specifically, I had to move some initialization code around for the
Ethernet to work properly after "ifconfig eth0 down ; ifconfig eth0 up".
Without these changes, the Ethernet doesn't come back "up" :(
The changes in this patch are done so that people WITH a PHY interrupt
have things done in the original order (I can't verify my change
against a system WITH PHY interrupts, so I preserved the order).
In short, this fix should be safe for all systems, but maybe
overly paranoid.
Anyone care to inspect and comment on the viability of this patch?
TIA
Dean Matsen
[-- Attachment #2: fec.patch.bz2 --]
[-- Type: application/x-bzip2, Size: 1284 bytes --]
reply other threads:[~2003-07-09 4:06 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=3F0B94B2.5090607@earthlink.net \
--to=deanmatsen@earthlink.net \
--cc=linuxppc-embedded@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.