From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] unhandled ethernet wakeup interrupt in 405 ethernet driver
Date: Tue, 10 May 2005 10:23:02 +0200 [thread overview]
Message-ID: <42806F66.4000508@esd-electronics.com> (raw)
In-Reply-To: <427B6E4A.9080402@esd-electronics.com>
Hi,
I came to the conslusion that the ethernet wakeup interupt should not be
touched by u-boot and the code can be removed.
Here is my patch that fixes cpu/ppc4xx/405gp_enet.c.
Here is the changelog entry:
* Patch by Matthias Fuchs, 10 May 2005:
Do not attach to ethernet wakeup interrupt in 405gp_enet.c
Does anything speak against this patch? I do not think so :-)
Matthias
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: enet_wakeup_irq-050510.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20050510/4268886a/attachment.txt
prev parent reply other threads:[~2005-05-10 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 13:16 [U-Boot-Users] unhandled ethernet wakeup interrupt in 405 ethernet driver Matthias Fuchs
2005-05-10 8:23 ` Matthias Fuchs [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=42806F66.4000508@esd-electronics.com \
--to=matthias.fuchs@esd-electronics.com \
--cc=u-boot@lists.denx.de \
/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