From: Markus Brunner <super.firetwister@googlemail.com>
To: benh@kernel.crashing.org
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Get new_emac driver running on 405EP
Date: Tue, 15 Apr 2008 23:51:41 +0200 [thread overview]
Message-ID: <200804152351.42651.super.firetwister@gmail.com> (raw)
In-Reply-To: <1208206961.6958.180.camel@pasglop>
On Monday 14 April 2008, Benjamin Herrenschmidt wrote:
> > 2) On the 405EP only the MDIO pin of the emac0 is pinned out, so both
> > phys have to be accessed through this one. This affectes the mdio
> > read/write functions.
>
> The later can easily be described in the device-tree as it's a fairly
> common setup.
mdio-device does the trick. This feature wasn't used by any other board in the
kernel yet.
I made another error. I did mix up the order of the MAL irqs, so the irq
handlers went mad. This was detected as a soft lock-up.
After correcting that both emacs are working on ppc405EP :).
Regards
Markus
next prev parent reply other threads:[~2008-04-15 21:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 17:38 Get new_emac driver running on 405EP M B
2008-04-14 21:02 ` Benjamin Herrenschmidt
2008-04-15 21:51 ` Markus Brunner [this message]
2008-04-16 1:43 ` Josh Boyer
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=200804152351.42651.super.firetwister@gmail.com \
--to=super.firetwister@googlemail.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).