From: James Chapman <jchapman@katalix.com>
To: Ron Bianco <ronb@lcsaudio.com>
Cc: Linuxppc-Embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: linuxppc tree with mv64xxx included?
Date: Wed, 02 Mar 2005 18:47:43 +0000 [thread overview]
Message-ID: <42260A4F.8030205@katalix.com> (raw)
In-Reply-To: <NCBBJPCHJLKAEAHINDCEGEJFFMAA.ronb@lcsaudio.com>
Ron Bianco wrote:
> I'm trying to locate the correct bitkeeper or other URL to get access to a
> linux 2.5 or 2.6 tree that includes the support for the marvell mv64xxx
> series chips.
> I've examined the emails in this list regarding related patches for clues,
> but am still confused.
>
> Tried bk://ppc.bkbits.net/linuxppc-2.5, but there is no marvell code.
There is Marvell code in that tree. Look in drivers/net/mv64*,
arch/ppc/syslib/mv*
Some boards are already ported. See arch/ppc/platforms/*
You'll also find the Marvell code in the "mainline" at
bk://linux.bkbits.net/linux-2.6
> We downloaded a 2.4.23 kernel tree directly from the marvell website, but it
> is lacking some things like i2c for marvell, that have been discussed here.
> Was further work, existing in some other tree, based on this?
i2c and several other improvements are in queue. Check the archives for
patches.
The latest ethernet code can be obtained from
bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
--
James Chapman
PGP key : http://www.katalix.com/~jchapman/pgpkey.txt
next prev parent reply other threads:[~2005-03-02 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 1:23 linuxppc tree with mv64xxx included? Ron Bianco
2005-03-01 1:33 ` Mark A. Greer
2005-03-02 18:47 ` James Chapman [this message]
2005-03-02 19:03 ` Ron Bianco
2005-03-02 20:35 ` Dale Farnsworth
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=42260A4F.8030205@katalix.com \
--to=jchapman@katalix.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=ronb@lcsaudio.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 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.