From mboxrd@z Thu Jan  1 00:00:00 1970
From: deferraz@terra.com.br (=?UTF-8?B?QW5kcsOp?= Ferraz)
Date: Mon, 9 Jan 2012 19:19:18 -0200
Subject: Some help about backporting a nic module to 2.6.32 longterm
Message-ID: <20120109191918.7dc7f32f@debo-air.ferraz.is-a-geek.net>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi,

	I'm using the 2.6.32.x longterm series for our servers but we
	are facing a problem with the bnx2x driver module in our latest
	G7 HP blade servers, the module exists but it doenst ping and
	cant access any node in the network, i saw too that the
	broadcom and hp driver specs can't build on 2.6.32 kernel
	because they only support the 2.6.18 redhat series. The version
	maintained by CentOS/Redhat om 5.x release works but it is
	based on 2.6.18 kernel.

	My initial idea was pull the CentOS 6 kernel source (based on
	2.6.32) and make a patch of the bnx2x driver for my kernel
	source, the patch applies but when i boot the kernel the
	version it remains the same, i saw that the /firmware directory
	has some bnx2x files on it, my question to you is that i
	couldnt find anywhere is how the .c file and the .fw
	correlates , or , how can i create a real backport of this
	driver so i can use an usable version of the driver for the
	longterm release?

	I'm starting to read Linux Device Drivers but i really don't
	know if this question will be answered on it, if you guys have
	more sources of information so i can read i'll be glad if
	send me some .

Thanks in advance,