* linuxppc tree with mv64xxx included?
@ 2005-03-01 1:23 Ron Bianco
2005-03-01 1:33 ` Mark A. Greer
2005-03-02 18:47 ` James Chapman
0 siblings, 2 replies; 5+ messages in thread
From: Ron Bianco @ 2005-03-01 1:23 UTC (permalink / raw)
To: Linuxppc-Embedded
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.
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?
FYI, we're bringing up a custom MPC7447A based board with the mv64462.
Thanks in advance,
Ron Bianco
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linuxppc tree with mv64xxx included?
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
1 sibling, 0 replies; 5+ messages in thread
From: Mark A. Greer @ 2005-03-01 1:33 UTC (permalink / raw)
To: Ron Bianco; +Cc: Linuxppc-Embedded
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.
>
Its in there along with a couple boards that use it. Note that the core
code is in arch/ppc/syslib in 2.6. The name of the main core file is
mv64x60.c.
There are also several patches sitting in the mm tree waiting to go in.
One of those patches adds an i2c driver.
Mark
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linuxppc tree with mv64xxx included?
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
2005-03-02 19:03 ` Ron Bianco
2005-03-02 20:35 ` Dale Farnsworth
1 sibling, 2 replies; 5+ messages in thread
From: James Chapman @ 2005-03-02 18:47 UTC (permalink / raw)
To: Ron Bianco; +Cc: Linuxppc-Embedded
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: linuxppc tree with mv64xxx included?
2005-03-02 18:47 ` James Chapman
@ 2005-03-02 19:03 ` Ron Bianco
2005-03-02 20:35 ` Dale Farnsworth
1 sibling, 0 replies; 5+ messages in thread
From: Ron Bianco @ 2005-03-02 19:03 UTC (permalink / raw)
To: James Chapman; +Cc: Linuxppc-Embedded
Thanks James and Mark,
I should have searched it rather than looking in 2.4 tree locations. :-P
We're going with 2.5 (2.6), but still getting familiar... many improvements
over 2.4.23.
Ron
> -----Original Message-----
> From: James Chapman [mailto:jchapman@katalix.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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: linuxppc tree with mv64xxx included?
2005-03-02 18:47 ` James Chapman
2005-03-02 19:03 ` Ron Bianco
@ 2005-03-02 20:35 ` Dale Farnsworth
1 sibling, 0 replies; 5+ messages in thread
From: Dale Farnsworth @ 2005-03-02 20:35 UTC (permalink / raw)
To: linuxppc-embedded
On Wed, Mar 02, 2005 at 06:47:43PM +0000, James Chapman wrote:
> The latest ethernet code can be obtained from
> bk://farnsworth.bkbits.net/linux-2.5-mv643xx-enet
Make that bk://dfarnsworth@bkbits.net/linux-2.5-mv643xx-enet
-Dale
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2005-03-02 20:35 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2005-03-02 19:03 ` Ron Bianco
2005-03-02 20:35 ` Dale Farnsworth
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).