From: Sven Luther <sven@powerlinux.fr>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Tzachi Perelstein <tzachi@marvell.com>,
Jeff Garzik <jeff@garzik.org>,
linuxppc-dev@ozlabs.org, netdev@vger.kernel.org,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [PATCH] pegasos_eth.c: Fix compile error over MV643XX_ defines
Date: Tue, 30 Oct 2007 10:36:06 +0100 [thread overview]
Message-ID: <20071030093606.GA20920@powerlinux.fr> (raw)
In-Reply-To: <43e72e890710300044o60bfc46cv8815226e39634996@mail.gmail.com>
On Tue, Oct 30, 2007 at 03:44:59AM -0400, Luis R. Rodriguez wrote:
> On 10/29/07, Dale Farnsworth <dale@farnsworth.org> wrote:
> > On Mon, Oct 29, 2007 at 05:27:29PM -0400, Luis R. Rodriguez wrote:
> > > This commit made an incorrect assumption:
> > > --
> > > Author: Lennert Buytenhek <buytenh@wantstofly.org>
> > > Date: Fri Oct 19 04:10:10 2007 +0200
> > >
> > > mv643xx_eth: Move ethernet register definitions into private header
> > >
> > > Move the mv643xx's ethernet-related register definitions from
> > > include/linux/mv643xx.h into drivers/net/mv643xx_eth.h, since
> > > they aren't of any use outside the ethernet driver.
> > >
> > > Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
> > > Acked-by: Tzachi Perelstein <tzachi@marvell.com>
> > > Signed-off-by: Dale Farnsworth <dale@farnsworth.org>
> > > --
> > >
> > > arch/powerpc/platforms/chrp/pegasos_eth.c made use of a 3 defines there.
> > >
> > > mcgrof@pogo:~/devel/wireless-2.6$ git-describe
> > >
> > > v2.6.24-rc1-138-g0119130
> > >
> > > This patch fixes this by internalizing 3 defines onto pegasos which are
> > > simply no longer available elsewhere. Without this your compile will fail
> >
> > That compile failure was fixed in commit
> > 30e69bf4cce16d4c2dcfd629a60fcd8e1aba9fee by Al Viro.
> >
> > However, as I examine that commit, I see that it defines offsets from
> > the eth block in the chip, rather than the full chip registeri block
> > as the Pegasos 2 code expects. So, I think it fixes the compile
> > failure, but leaves the Pegasos 2 broken.
> >
> > Luis, do you have Pegasos 2 hardware? Can you (or anyone) verify that
> > the following patch is needed for the Pegasos 2?
>
> Nope, sorry.
I am busy right now, but have various pegasos machines available for
testing. What exactly should i test ?
Friendly,
Sven Luther
next prev parent reply other threads:[~2007-10-30 9:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:27 [PATCH] pegasos_eth.c: Fix compile error over MV643XX_ defines Luis R. Rodriguez
2007-10-29 22:39 ` Dale Farnsworth
2007-10-30 7:44 ` Luis R. Rodriguez
2007-10-30 9:36 ` Sven Luther [this message]
2007-10-30 10:22 ` Dale Farnsworth
2007-10-30 18:32 ` Jeff Garzik
2007-10-29 22:47 ` Lennert Buytenhek
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=20071030093606.GA20920@powerlinux.fr \
--to=sven@powerlinux.fr \
--cc=buytenh@wantstofly.org \
--cc=jeff@garzik.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mcgrof@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=tzachi@marvell.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;
as well as URLs for NNTP newsgroup(s).