From: "Mark A. Greer" <mgreer@mvista.com>
To: Ashish Bijlani <ashish.bijlani@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC7447A based board with MV64462 Marvell Discovery III controller
Date: Thu, 13 Oct 2005 11:26:54 -0700 [thread overview]
Message-ID: <20051013182654.GA18497@mag.az.mvista.com> (raw)
In-Reply-To: <ec55b17e0510130042m6c6c0c43ndf09f40a03f9cf97@mail.gmail.com>
On Thu, Oct 13, 2005 at 01:12:19PM +0530, Ashish Bijlani wrote:
> Hi,
>
> I'm trying to bring MPC7447A based board with MV64462 Marvell Discovery III
> controller up. Can you guide me to Linux-2.6 sources with support for
> MV64462 Marvell Discovery III controller and MPC7447A PowerPC processor.
> Support for I2c, dual 10/100/1000 ethernet ports, and relevant platform
> should be there. I cannot access the bit keeper repositories so please guide
> me to the linux-2.6 kernel source tree if you can.
Ashish,
Support for both the 7447A and mv64x6x is in the latest 2.6 mainline
kernel source at kernel.org.
If your board is a chrp/openfirmware board, then you probably want to use
the Pegasos code as an example. If your board has U-boot or some other
non-OF firmware, then use the katana or chestnut as an example (katana
is more up-to-date than the chestnut). The ev64360 code may help too.
There are i2c and enet drivers (and mpsc and wdt) in that source as well.
Note that I've never had a 64462 to test with. Since the '2' means it
has less functionality than the '0', you may run into some problems.
If you do, please let me know what they are.
Mark
next prev parent reply other threads:[~2005-10-13 18:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-13 7:42 MPC7447A based board with MV64462 Marvell Discovery III controller Ashish Bijlani
2005-10-13 18:26 ` Mark A. Greer [this message]
2005-10-20 15:04 ` Sven Luther
2005-10-20 15:21 ` Mark A. Greer
2005-10-20 15:37 ` Sven Luther
2005-10-21 3:50 ` Kumar Gala
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=20051013182654.GA18497@mag.az.mvista.com \
--to=mgreer@mvista.com \
--cc=ashish.bijlani@gmail.com \
--cc=linuxppc-embedded@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