From: Scott Wood <scottwood@freescale.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] FCC: fix confused base / offset
Date: Wed, 09 Apr 2008 12:39:48 -0500 [thread overview]
Message-ID: <47FCFF64.9050109@freescale.com> (raw)
In-Reply-To: <20080409165324.GF10465@pengutronix.de>
Sascha Hauer wrote:
> Right, so it's probably not worth the effort. I stumbled on this while
> porting my board to the new binding code. I was quite confused when
> seeing this so I made this fix to understand what's going on here.
>
> BTW have you tested the FCC driver with the new binding code?
Yes.
> I do not
> manage to get it working. Everything seems to be fine but
> fs_enet_start_xmit does not send a packet and no interrupts are
> arriving.
What does your device tree look like? Are all the pins and clocks set
up properly? Does the PHY negotiate OK? Is any error reported in the
descriptor?
>> Does this break arch/ppc, BTW?
>
> Yes. arch=ppc is out of my scope, so I forget about it regularly, sorry.
> It breaks arch/ppc/platforms/mpc8272ads_setup.c which can be easily
> fixed though. But as the mpc8272ads is supported with arch=powerpc,
> shouldn't it go away anyway?
arch/ppc is going away entirely in June or so. !CONFIG_PPC_NEW_BINDING
in arch/powerpc is going away as soon as I can unlazy myself enough to
send a patch. :-)
-Scott
next prev parent reply other threads:[~2008-04-09 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 13:06 [PATCH] FCC: fix confused base / offset Sascha Hauer
2008-04-09 16:11 ` Scott Wood
2008-04-09 16:53 ` Sascha Hauer
2008-04-09 17:39 ` Scott Wood [this message]
2008-04-10 10:46 ` Sascha Hauer
2008-04-10 16:38 ` Scott Wood
2008-04-14 14:47 ` Sascha Hauer
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=47FCFF64.9050109@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=s.hauer@pengutronix.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;
as well as URLs for NNTP newsgroup(s).