public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Moschip MCS8142 SoC
Date: Fri, 6 Dec 2013 03:31:31 +0100	[thread overview]
Message-ID: <201312060331.31958.arnd@arndb.de> (raw)
In-Reply-To: <OF433D4F00.CB35F8E7-ON86257C37.004F3E8D@rockwellcollins.com>

On Wednesday 04 December 2013, mlweber1 at rockwellcollins.com wrote:
> Has anyone happened to work with this Moschip SoC?  I found Linux BSP 
> patches for the MCS8140 (OpenWRT 3.3 Kernel plus some initial attempts at 
> mainlining around 3.7), however that MCS8140 SoC was a true ARMv5 compared 
> to the MCS8142 which seems to be based on a Faraday fa526 ARMv4.  
> Another item I'm not to sure about is if the bus and peripheral 
> architecture are similar.
> 
> Any help is appreciated (reference docs that outline the register 
> definition, etc.) .  We're trying to get a 3.x kernel running on this 
> target to replace a older 2.6.24 blob that we can't get source for..... 
> 
> Matthew L Weber / Sr Software Engineer / Platform SW 

Hi Matthew,

Florian Fainelli (now on Cc) did the patch series for MCS814x in the past,
see http://lwn.net/Articles/507006/. As far as I understand, MCS8140
and MCS8142 only differ in the CPU core, so the required code is actually
almost identical.
However, I would now recommend doing the port on the latest kernel version,
i.e. 3.13 at this point, for which you would not be able to reuse
much of the code, as we have redone all the interfaces to make it simpler
to add a new platform. Essentially you add separate drivers to 
drivers/irqchip, drivers/clocksource, drivers/clk, arch/arm/include/debug
and drivers/pci/host but won't need any actual code in arch/arm/mach-* any
more at this point.

Jonas Jensen is working on support for the "moxart" platform, which uses
the same fa526 core and which is similar in other regards, so I'd recommend
looking at his code as examples for how to do this the right way.

	Arnd

  reply	other threads:[~2013-12-06  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-04 14:25 Moschip MCS8142 SoC mlweber1 at rockwellcollins.com
2013-12-06  2:31 ` Arnd Bergmann [this message]
     [not found]   ` <CAGVrzcYWzb95j2qVKWqZ1iVrR9Ak8bX6ej8hZS_6TQ_eEBp+pg@mail.gmail.com>
2013-12-06  2:53     ` Arnd Bergmann
2013-12-06  3:32   ` mlweber1 at rockwellcollins.com
2013-12-06 16:19     ` Arnd Bergmann

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=201312060331.31958.arnd@arndb.de \
    --to=arnd@arndb.de \
    --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