On Mon, Jul 02, 2007 at 04:52:52PM -0700, Williams, Mitch A wrote:
- We include e1000new in 2.6.23, along side e1000. We expose ICH9
device IDs in e1000new, and gate the rest of the IDs inside
#ifndef CONFIG_E1000.
No. Hardware support in one driver should never be affected by config
Christoph Hellwig wrote:
On Mon, Jul 02, 2007 at 04:52:52PM -0700, Williams, Mitch A wrote:
- We include e1000new in 2.6.23, along side e1000. We expose ICH9
device IDs in e1000new, and gate the rest of the IDs inside
#ifndef CONFIG_E1000.
No. Hardware support in one driver should never
Mark McLoughlin wrote:
I disagree, we should not break the current e1000 driver in
the kernel while
there is a new driver coming up that introduces ich9 support
without breaking
(the old e1000) support for all other devices. This is why
we want to drop a new
version of the e1000
There seems to be a lot of concern over obsoleting the e1000 driver
too quickly, and with confusing users (and startup scripts) about which
driver to load.
Yes.
Obviously, we at Intel want to get e1000new into the kernel as quickly
as possible, and to obsolete e1000 also as quickly as
Sorry if this is a duplication, I forgot to switch to plain text.
On 6/29/07, Jim McCullough [EMAIL PROTECTED] wrote:
It goes back to ICH7 for the PCIe support. That also includes models used as
plugin PCIe devices. I dont remember if ICH6 erra devices were PCI or PCIe.
I'll leave that
Jim McCullough wrote:
It goes back to ICH7 for the PCIe support. That also includes models used
as plugin PCIe devices. I dont remember if ICH6 erra devices were PCI or
PCIe. I'll leave that part for Auke.
On 6/29/07, Jeff Garzik [EMAIL PROTECTED] wrote:
Andrew Grover wrote:
I think making
