From: Divy Le Ray <divy@chelsio.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
swise@opengridcomputing.com
Subject: Re: [PATCH 1/10] cxgb3 - main header files
Date: Tue, 09 Jan 2007 02:19:14 -0800 [thread overview]
Message-ID: <45A36C22.6010009@chelsio.com> (raw)
In-Reply-To: <45918CA4.3020601@garzik.org>
Jeff Garzik wrote:
> Divy Le Ray wrote:
>> From: Divy Le Ray <divy@chelsio.com>
>>
>> This patch implements the main header files of
>> the Chelsio T3 network driver.
>>
>> Signed-off-by: Divy Le Ray <divy@chelsio.com>
>
> Once you think it's ready, email me a URL to a single patch that adds
> the driver to the latest linux-2.6.git kernel. Include in the email a
> description of the driver and signed-off-by line, which will get
> directly included in the git changelog.
>
> Adding new drivers is a bit special, because we want to merge it as a
> single changeset, but that would create a patch too large to review on
> the common kernel mailing lists.
Jeff,
You can grab the monolithic patch at this URL:
http://service.chelsio.com/kernel.org/cxgb3.patch.bz2
This patch adds support for the latest 1G/10G Chelsio adapter, T3.
It is required by the T3 RDMA driver Steve Wise submitted.
Here is a brief description of its content:
drivers/net/cxgb3/adapter.h,
drivers/net/cxgb3/common.h,
drivers/net/cxgb3/cxgb3_ioctl.h,
drivers/net/cxgb3/firmware_exports.h:
main header files
drivers/net/cxgb3/cxgb3_main.c
main source file
drivers/net/cxgb3/t3_hw.c
HW access routines
drivers/net/cxgb3/sge.c,
drivers/net/cxgb3/sge_defs.h
scatter/gather engine
drivers/net/cxgb3/ael1002.c,
drivers/net/cxgb3/mc5.c,
drivers/net/cxgb3/vsc8211.c,
drivers/net/cxgb3/xgmac.c
on board memory, MAC and PHY management
drivers/net/cxgb3/cxgb3_ctl_defs.h,
drivers/net/cxgb3/cxgb3_defs.h,
drivers/net/cxgb3/cxgb3_offload.h,
drivers/net/cxgb3/l2t.h, drivers/net/cxgb3/t3_cpl.h,
drivers/net/cxgb3/t3cdev.h
offload operations header files
drivers/net/cxgb3/cxgb3_offload.c,
drivers/net/cxgb3/l2t.c
offload capabilities
drivers/net/cxgb3/regs.h
register definitions
drivers/net/Kconfig
drivers/net/Makefile
drivers/net/cxgb3/Makefile
drivers/net/cxgb3/version.h
build files and versioning
Signed-off-by: Divy Le Ray <divy@chelsio.com>
---
next prev parent reply other threads:[~2007-01-09 10:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 12:41 [PATCH 1/10] cxgb3 - main header files Divy Le Ray
2006-12-26 20:57 ` Jeff Garzik
2006-12-27 8:52 ` Divy Le Ray
2006-12-27 9:03 ` Arjan van de Ven
2007-01-09 10:19 ` Divy Le Ray [this message]
2007-01-09 10:28 ` Jeff Garzik
2007-01-09 13:38 ` Steve Wise
2007-01-09 13:57 ` Michael S. Tsirkin
2007-01-09 14:46 ` Steve Wise
2007-01-09 19:39 ` [openib-general] " Steve Wise
2007-01-09 18:29 ` Caitlin Bestler
2007-01-09 16:28 ` Roland Dreier
2007-01-09 16:41 ` Jeff Garzik
2007-01-09 17:09 ` Roland Dreier
2007-01-19 3:05 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 7:20 Divy Le Ray
2006-12-14 5:41 Divy Le Ray
2006-12-08 3:26 Divy Le Ray
2006-12-04 19:44 Divy Le Ray
2006-11-17 20:23 Divy Le Ray <divy@chelsio.com>
2006-11-17 20:49 ` Stephen Hemminger
2006-11-17 21:48 ` Roland Dreier
2006-11-18 17:25 ` Jan Engelhardt
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=45A36C22.6010009@chelsio.com \
--to=divy@chelsio.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=swise@opengridcomputing.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).