From: Pradeep Dalvi <pradeep@netxen.com>
To: netdev@vger.kernel.org
Cc: Jeff Garzik <jeff@garzik.org>,
Sanjeev Jorapur <sanjeev@netxen.com>, Rob Mapes <rob@netxen.com>,
unmproj@linsyssoft.com, brazilnut@us.ibm.com, wendyx@us.ibm.com,
"Amit S. Kale" <amitkale@netxen.com>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: [PATCH 2.6.18-rc7 9/9] NetXen: CRB reg definitions
Date: Tue, 19 Sep 2006 08:32:26 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0609190830490.25990@dut39> (raw)
In-Reply-To: <Pine.LNX.4.64.0609151201320.7710@dut39>
diff -u linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_phan_reg.h linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_phan_reg.h
--- linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_phan_reg.h 2006-09-15 10:51:59.000000000 -0700
+++ linux-2.6.18-rc7/drivers/net/netxen/netxen_nic_phan_reg.h 2006-09-19 07:51:20.000000000 -0700
@@ -30,26 +30,26 @@
#ifndef __NIC_PHAN_REG_H_
#define __NIC_PHAN_REG_H_
-/**
- * CRB Registers or queue message done only at initialization time....
- **/
+/*
+ * CRB Registers or queue message done only at initialization time.
+ */
-/**
+/*
* The following 2 are the base adresses for the CRB registers and their
- * offsets will be added to get addresses for the index addresses.......
- **/
+ * offsets will be added to get addresses for the index addresses.
+ */
#define NIC_CRB_BASE_PORT1 NETXEN_CAM_RAM(0x200)
#define NIC_CRB_BASE_PORT2 NETXEN_CAM_RAM(0x250)
#define NETXEN_NIC_REG(X) (NIC_CRB_BASE_PORT1+(X))
-/**
+/*
* CrbPortPhanCntrHi/Lo is used to pass the address of HostPhantomIndex address
* which can be read by the Phantom host to get producer/consumer indexes from
* Phantom/Casper. If it is not HOST_SHARED_MEMORY, then the following
* registers will be used for the addresses of the ring's shared memory
* on the Phantom.
- **/
+ */
#define CRB_PHAN_CNTRL_LO_OFFSET NETXEN_NIC_REG(0x00)
#define CRB_PHAN_CNTRL_HI_OFFSET NETXEN_NIC_REG(0x04)
prev parent reply other threads:[~2006-09-19 15:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-15 18:33 [PATCH 2.6.18-rc7 0/9] NetXen: 1G/10G Ethernet Driver Amit S. Kale
2006-09-15 18:39 ` [PATCH 2.6.18-rc7 1/9] NetXen: Makefile and driver main file Amit S. Kale
2006-09-19 15:18 ` Pradeep Dalvi
2006-09-15 18:40 ` [PATCH 2.6.18-rc7 2/9] NetXen: Hardware access routines Amit S. Kale
2006-09-19 15:20 ` Pradeep Dalvi
2006-09-15 18:44 ` [PATCH 2.6.18-rc7 3/9] NetXen: hw initilization routines Amit S. Kale
2006-09-19 15:23 ` Pradeep Dalvi
2006-09-15 18:45 ` [PATCH 2.6.18-rc7 4/9] NetXen: intr routines and niu handling Amit S. Kale
2006-09-19 15:25 ` Pradeep Dalvi
2006-09-15 18:48 ` [PATCH 2.6.18-rc7 5/9] NetXen: ethtool interface Amit S. Kale
2006-09-19 15:26 ` Pradeep Dalvi
2006-09-15 18:51 ` [PATCH 2.6.18-rc7 6/9] NetXen: Main header file Amit S. Kale
2006-09-15 19:41 ` Randy.Dunlap
2006-09-19 15:28 ` Pradeep Dalvi
2006-09-15 18:57 ` [PATCH 2.6.18-rc7 7/9] NetXen: hw access routines " Amit S. Kale
2006-09-19 15:30 ` Pradeep Dalvi
2006-09-15 19:01 ` [PATCH 2.6.18-rc7 8/9] NetXen: Header file and ioctl " Amit S. Kale
2006-09-15 19:04 ` [PATCH 2.6.18-rc7 9/9] NetXen: CRB reg definitions Amit S. Kale
2006-09-19 15:32 ` Pradeep Dalvi [this message]
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=Pine.LNX.4.64.0609190830490.25990@dut39 \
--to=pradeep@netxen.com \
--cc=amitkale@netxen.com \
--cc=brazilnut@us.ibm.com \
--cc=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rob@netxen.com \
--cc=sanjeev@netxen.com \
--cc=unmproj@linsyssoft.com \
--cc=wendyx@us.ibm.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