From: deferraz@terra.com.br (André Ferraz)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Some help about backporting a nic module to 2.6.32 longterm
Date: Mon, 9 Jan 2012 19:19:18 -0200 [thread overview]
Message-ID: <20120109191918.7dc7f32f@debo-air.ferraz.is-a-geek.net> (raw)
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,
next reply other threads:[~2012-01-09 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 21:19 André Ferraz [this message]
2012-01-09 22:49 ` Some help about backporting a nic module to 2.6.32 longterm Greg KH
2012-01-10 1:08 ` André Ferraz
2012-01-10 1:30 ` Greg KH
2012-01-11 21:42 ` André Ferraz
2012-01-11 22:13 ` Greg KH
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=20120109191918.7dc7f32f@debo-air.ferraz.is-a-geek.net \
--to=deferraz@terra.com.br \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).