From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Freescale fec.c driver breakage
Date: Tue, 5 Jun 2012 13:40:37 +0100 [thread overview]
Message-ID: <20120605124037.GT23408@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FCDFD4E.1000906@snapgear.com>
On Tue, Jun 05, 2012 at 10:36:30PM +1000, Greg Ungerer wrote:
> I am pretty sure AHB was bolted on later. This FEC core has progressed
> from very old Motorola PowerPC platforms to ColdFire/M68k to ARM, over
> something coming close to a 20 year period. In the earlier uses of it
> there is quite a few differences (including some quite odd register
> layout differences).
> There may be other things that are somewhat like an ahb clock and ipg
> clock, but really these are things that have come along later with a
> specific platform implementation.
For AHB that sounds plausible, but for the IPG clock (assuming I've
identified the function correctly) I've got a very hard time believing
that the IP ever didn't need a clock - my understanding is that it's the
master clock for the IP ("IP gate").
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120605/25fb6aef/attachment.sig>
next prev parent reply other threads:[~2012-06-05 12:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 4:42 Freescale fec.c driver breakage Greg Ungerer
2012-06-04 8:19 ` Sascha Hauer
2012-06-04 9:16 ` Mark Brown
2012-06-05 6:55 ` Greg Ungerer
2012-06-05 9:41 ` Mark Brown
2012-06-05 12:17 ` Greg Ungerer
2012-06-05 12:24 ` Mark Brown
2012-06-05 12:36 ` Greg Ungerer
2012-06-05 12:40 ` Mark Brown [this message]
2012-06-05 12:48 ` Sascha Hauer
2012-06-05 13:24 ` Greg Ungerer
2012-06-05 13:41 ` Mark Brown
2012-06-05 14:35 ` Steven King
2012-06-06 7:41 ` Greg Ungerer
2012-06-07 23:36 ` Mark Brown
2012-06-05 13:42 ` 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=20120605124037.GT23408@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.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).