From: Sven Luther <sven.luther@wanadoo.fr>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MPC7447A based board with MV64462 Marvell Discovery III controller
Date: Thu, 20 Oct 2005 17:04:50 +0200 [thread overview]
Message-ID: <20051020150450.GA27704@localhost.localdomain> (raw)
In-Reply-To: <20051013182654.GA18497@mag.az.mvista.com>
On Thu, Oct 13, 2005 at 11:26:54AM -0700, Mark A. Greer wrote:
> 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
Hey, we have code to boot the Freeserv with chrp/Of, need to clean it up and
merge it though. Would this be a good thing to submit for mainline inclusion,
it is a couple of lines at most, altough there is some reuse of the interrupt
controller code i think, which needs some cleanup.
Friendly,
Sven Luther
next prev parent reply other threads:[~2005-10-20 15:40 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
2005-10-20 15:04 ` Sven Luther [this message]
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=20051020150450.GA27704@localhost.localdomain \
--to=sven.luther@wanadoo.fr \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@mvista.com \
/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