From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] Moschip MCS8142 SoC
Date: Tue, 3 Dec 2013 06:52:57 +0200 [thread overview]
Message-ID: <20131203045257.GJ3720@tarshish> (raw)
In-Reply-To: <OFA1E9F549.035B351F-ON86257C36.00138A7C-86257C36.001656E7@rockwellcollins.com>
Hi Matthew,
On Mon, Dec 02, 2013 at 10:04:00PM -0600, Matthew Weber 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 seems to be based on a Faraday fa526 ARMv4. Plus I'm not
> to sure if the bus and peripheral architecture are simliar (need to do a
> little more research yet).
>
> 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.....
You have better chances of getting useful answers at the linux-arm-kernel
mailing list (linux-arm-kernel at lists.infradead.org).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2013-12-03 4:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 18:10 [Buildroot] [PATCH 1/1] Add support to set the default port for dropbear to listen on jeroen.de.wachter at telenet.be
2013-11-22 19:52 ` Thomas De Schampheleire
2013-11-22 20:17 ` Arnout Vandecappelle
2013-11-22 20:58 ` Yann E. MORIN
2013-11-22 22:14 ` Peter Korsgaard
2013-12-03 4:04 ` [Buildroot] Moschip MCS8142 SoC Matthew Weber
2013-12-03 4:52 ` Baruch Siach [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=20131203045257.GJ3720@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.