public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "Morten P.D. Stevens" <mstevens@win-professional.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Xeon 5500 series support in kernel
Date: Sun, 5 Jul 2009 11:55:20 +0200	[thread overview]
Message-ID: <20090705095520.GP2041@one.firstfloor.org> (raw)
In-Reply-To: <520B2A28AACEE94388C511BBB834933707AA86AEA1@IGR-IMC-01.corp.win-professional.com>

On Sat, Jul 04, 2009 at 08:01:44PM +0200, Morten P.D. Stevens wrote:
> Hi Andi,
> 
> a general question with regard to the new intel nehalem platform:
> 
> Which linux version is needed for an intel nehalem based xeon in view of the new intel 5500/5520 chipset drivers?
> 
> Does it work with 2.6.18? (Debian Etch)

You would need backported drivers for Ethernet etc; the plain
integrated drivers in 2.6.18 will not work. The e1000 project
at sourceforge has driver backports for Ethernet.

I don't know if Debian does regular backports of drivers,
some other distributions with support for old kernels do.

Also some power saving features and performance features 
which are related to power saving (turbo mode) will not work in that old a 
kernel. For full performance it's better to use newer kernels or
kernels with appropiate backports.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2009-07-05  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  8:59 Xeon 5500 series support in kernel xb
2009-07-02  9:46 ` Andi Kleen
2009-07-04 11:41   ` Nix
2009-07-04 16:07     ` Andi Kleen
2009-07-04 18:01       ` Morten P.D. Stevens
2009-07-05  9:55         ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-07-02  7:45 lchampig

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=20090705095520.GP2041@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mstevens@win-professional.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