From: Ilya Yanok <yanok@emcraft.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3][v3] dnet: driver for Dave DNET ethernet controller
Date: Mon, 09 Feb 2009 15:39:31 +0300 [thread overview]
Message-ID: <49902403.2010406@emcraft.com> (raw)
In-Reply-To: <498FD452.2010501@gmail.com>
Hi Ben,
thanks for review.
Ben Warren wrote:
>> @@ -69,6 +70,7 @@ COBJS-$(CONFIG_ULI526X) += uli526x.o
>> COBJS-$(CONFIG_VSC7385_ENET) += vsc7385.o
>> COBJS-$(CONFIG_XILINX_EMAC) += xilinx_emac.o
>> COBJS-$(CONFIG_XILINX_EMACLITE) += xilinx_emaclite.o
>> +COBJS-$(CONFIG_SH_ETHER) += sh_eth.o
>>
> Why is the SH driver affected?, or is this a merge artifact?
Uh... Sorry. Yes, it's merge artifact.
> <snip>
>> +struct dnet_registers {
>> + /* ALL DNET FIFO REGISTERS */
>> + u32 RX_LEN_FIFO;
>> + u32 RX_DATA_FIFO;
>> + u32 TX_LEN_FIFO;
>> + u32 TX_DATA_FIFO;
>> + u32 pad1[0x3c];
>> + /* ALL DNET CONTROL/STATUS REGISTERS */
>> + u32 VERCAPS;
>> + u32 INTR_SRC;
>> + u32 INTR_ENB;
>> + u32 RX_STATUS;
>> + u32 TX_STATUS;
>> + u32 RX_FRAMES_CNT;
>> + u32 TX_FRAMES_CNT;
>> + u32 RX_FIFO_TH;
>> + u32 TX_FIFO_TH;
>> + u32 SYS_CTL;
>> + u32 PAUSE_TMR;
>> + u32 RX_FIFO_WCNT;
>> + u32 TX_FIFO_WCNT;
>> + u32 pad2[0x33];
>> + /* ALL DNET MAC REGISTERS */
>> + u32 MACREG_DATA; /* Mac-Reg Data */
>> + u32 MACREG_ADDR; /* Mac-Reg Addr */
>> + u32 pad3[0x3e];
>> + /* ALL DNET RX STATISTICS COUNTERS */
>> + u32 RX_PKT_IGNR_CNT;
>> + u32 RX_LEN_CHK_ERR_CNT;
>> + u32 RX_LNG_FRM_CNT;
>> + u32 RX_SHRT_FRM_CNT;
>> + u32 RX_IPG_VIOL_CNT;
>> + u32 RX_CRC_ERR_CNT;
>> + u32 RX_OK_PKT_CNT;
>> + u32 RX_CTL_FRM_CNT;
>> + u32 RX_PAUSE_FRM_CNT;
>> + u32 RX_MULTICAST_CNT;
>> + u32 RX_BROADCAST_CNT;
>> + u32 RX_VLAN_TAG_CNT;
>> + u32 RX_PRE_SHRINK_CNT;
>> + u32 RX_DRIB_NIB_CNT;
>> + u32 RX_UNSUP_OPCD_CNT;
>> + u32 RX_BYTE_CNT;
>> + u32 pad4[0x30];
>> + /* DNET TX STATISTICS COUNTERS */
>> + u32 TX_UNICAST_CNT;
>> + u32 TX_PAUSE_FRM_CNT;
>> + u32 TX_MULTICAST_CNT;
>> + u32 TX_BRDCAST_CNT;
>> + u32 TX_VLAN_TAG_CNT;
>> + u32 TX_BAD_FCS_CNT;
>> + u32 TX_JUMBO_CNT;
>> + u32 TX_BYTE_CNT;
>> +} __attribute__((packed));
>>
> Why is this packed? All fields are 32-bit aligned already.
Generally, I prefer declaring such structures with ((packed)) regardless
of if it's really do something. Just to show that it should be packed.
Regards, Ilya.
next prev parent reply other threads:[~2009-02-09 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-07 21:59 [U-Boot] [PATCH 0/3][v3] qong: support for Dave/DENX QongEVB-LITE Ilya Yanok
2009-02-07 21:59 ` [U-Boot] [PATCH 1/3][v3] mx31: add GPIO registers definitions Ilya Yanok
2009-02-07 22:30 ` Jean-Christophe PLAGNIOL-VILLARD
2009-02-07 21:59 ` [U-Boot] [PATCH 2/3][v3] dnet: driver for Dave DNET ethernet controller Ilya Yanok
2009-02-09 6:59 ` Ben Warren
2009-02-09 12:39 ` Ilya Yanok [this message]
2009-02-09 14:27 ` Wolfgang Denk
2009-02-09 17:21 ` Ilya Yanok
2009-02-09 17:24 ` [U-Boot] [PATCH 2/3][v4] " Ilya Yanok
2009-02-09 17:44 ` [U-Boot] [PATCH 2/3][v3] " Ilya Yanok
2009-02-09 17:45 ` [U-Boot] [PATCH 2/3][v5] " Ilya Yanok
2009-02-09 17:51 ` Jean-Christophe PLAGNIOL-VILLARD
2009-02-09 17:55 ` Ben Warren
2009-02-07 21:59 ` [U-Boot] [PATCH 3/3][v3] qong: support for Dave/DENX QongEVB-LITE board Ilya Yanok
2009-02-09 23:25 ` [U-Boot] [PATCH 0/3][v3] qong: support for Dave/DENX QongEVB-LITE Jean-Christophe PLAGNIOL-VILLARD
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=49902403.2010406@emcraft.com \
--to=yanok@emcraft.com \
--cc=u-boot@lists.denx.de \
/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