[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20081013183503.GA28133@cs181140183.pp.htv.fi>
Date: Mon, 13 Oct 2008 21:35:03 +0300
From: Adrian Bunk <bunk@...nel.org>
To: Brice Goglin <brice@...i.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Jeff Garzik <jgarzik@...hat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
linux-kernel@...r.kernel.org, apw@...dowen.org,
linuxppc-dev@...abs.org, sam@...nborg.org,
e1000-devel@...ts.sourceforge.net, netdev@...r.kernel.org,
"Sosnowski, Maciej" <maciej.sosnowski@...el.com>
Subject: Re: [BUILD_FAILURE] 2.6.27-git2 - allyesconfig on powerpc
selectsCONFIG_INTEL_IOATDMA=y
On Mon, Oct 13, 2008 at 08:21:45PM +0200, Brice Goglin wrote:
> Brandeburg, Jesse wrote:
> > What we want, is myri10ge and ixgbe drivers that can build whether or not CONFIG_INTEL_IOATDMA is enabled. IF CONFIG_INTEL_IOATDMA *is* enabled (which it should not be on PPC) then there are several cases we want to work:
> > CONFIG_INTEL_IOATDMA=m ---> CONFIG_IXGBE=[m|n]
> > CONFIG_INTEL_IOATDMA=y ---> CONFIG_IXGBE=[m|y|n]
> > CONFIG_INTEL_IOATDMA=n ---> CONFIG_IXGBE=[m|y|n]
> > CONFIG_INTEL_IOATDMA depends on X86
>
> I am not sure I want to prevent myri10ge=y just because ioatdma=m.
>...
Technically both solutions are possible, which to choose is just a
policy decision you have to agree on.
In practice it will anyway only rarely matter.
But considering that igb is in a similar situation it would be nice if
all 3 drivers would handle it the same way.
> Brice
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists