netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Vlad Zolotarov" <vladz@broadcom.com>
To: "Dave Miller" <davem@davemloft.net>,
	"Michael Chan" <mchan@broadcom.com>,
	"Bhanu (Venkata Bhanu Prakash) Gollapudi" <bprakash@broadcom.com>
Cc: "Eilon Greenstein" <eilong@broadcom.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Dmitry Kravkov" <dmitry@broadcom.com>,
	"Yaniv Rosner" <yaniv.rosner@broadcom.com>,
	"David Woodhouse" <dwmw2@infradead.org>
Subject: [PATCH net-next 0/24] bnx2x: New FW and support for 578xx
Date: Tue, 14 Jun 2011 14:32:31 +0300	[thread overview]
Message-ID: <201106141432.32257.vladz@broadcom.com> (raw)
In-Reply-To: <BD3F7F1EFBA6D54DB056C4FFA451400809D2C13864@SJEXCHCCR01.corp.ad.broadcom.com>

Dave, pls., consider applying this patch series.

This patch series introduce support for the new 578x0 chip series and
therefore includes new 7.0.20 FW:
	1) New LINK code.
	2) Absolutely new HSI that allows supporting different chips in more
consolidated way, which caused a significant changes in the driver code
including moving the HSI handling code into a spearate files (patches 11
and 12).

We also send the new FW files to David Woodhouse. It's the first time we
submit to the linux-firmware git so I hope we don't mess the things up: we
DO NOT patch firmware/WHENCE and firmware/Makefile files in our net-next
patches and we patch the WHENCE file in the linux-firmware patch. Dave,
pls., confirm if it's a correct procedure.

If it is, pls., note that the bnx2x driver will compile but won't work
until u integrate the new FW into the kernel tree.

You may alsofind these patches at our public site.
	net-next series at http://linux.broadcom.com/eilong/1.70.00-0/
	New FW at http://linux.broadcom.com/eilong/FW-7.0.20.0/
 
Thanks,
vlad


       reply	other threads:[~2011-06-14 11:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201106141213.34576.vladz@broadcom.com>
     [not found] ` <BD3F7F1EFBA6D54DB056C4FFA451400809D2C13864@SJEXCHCCR01.corp.ad.broadcom.com>
2011-06-14 11:32   ` Vlad Zolotarov [this message]
2011-06-14 15:54     ` [PATCH net-next 0/24] bnx2x: New FW and support for 578xx David Miller
2011-06-14 16:22       ` Vlad Zolotarov
2011-06-14 17:32         ` David Miller
2011-06-14 17:35           ` Michael Chan
2011-06-14 17:46             ` David Miller
2011-06-14 18:32               ` Vladislav Zolotarov
2011-06-14 18:33                 ` David Miller
2011-06-14 19:23                   ` David Woodhouse
2011-06-14 18:52               ` David Woodhouse
2011-07-18  9:48       ` Eric Dumazet
2011-07-18  9:55         ` Eilon Greenstein
2011-07-18 10:09           ` Eric Dumazet
2011-06-15 15:09     ` David Miller

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=201106141432.32257.vladz@broadcom.com \
    --to=vladz@broadcom.com \
    --cc=bprakash@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=dmitry@broadcom.com \
    --cc=dwmw2@infradead.org \
    --cc=eilong@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=yaniv.rosner@broadcom.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;
as well as URLs for NNTP newsgroup(s).