From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/4] net: Move Emaclite to NET_MULTI
Date: Mon, 11 Oct 2010 11:37:09 +1000 [thread overview]
Message-ID: <4CB26A45.7020004@monstr.eu> (raw)
In-Reply-To: <4C7DE91A.4040102@gmail.com>
Hi Ben,
Ben Warren wrote:
> Hi Michal,
>
> Sorry for the delay in reviewing
>
> On 8/2/2010 5:49 AM, Michal Simek wrote:
>> Emaclite was using old net api that's why
>> this patch move emaclite to NET_MULTI api.
>>
>> Signed-off-by: Michal Simek<monstr@monstr.eu>
>> ---
>> drivers/net/xilinx_emaclite.c | 84
>> +++++++++++++++++++++++------------------
>> include/netdev.h | 1 +
>> 2 files changed, 48 insertions(+), 37 deletions(-)
>>
>> diff --git a/drivers/net/xilinx_emaclite.c
>> b/drivers/net/xilinx_emaclite.c
>> index 0820daa..f460525 100644
...
>> * TX - TX_PING& TX_PONG initialization
>> @@ -158,7 +145,7 @@ int eth_init (bd_t * bis)
>> /* Restart PING TX */
>> out_be32 (emaclite.baseaddress + XEL_TSR_OFFSET, 0);
>> /* Copy MAC address */
>> - xemaclite_alignedwrite (enetaddr,
>> + xemaclite_alignedwrite (dev->enetaddr,
>> emaclite.baseaddress, ENET_ADDR_LENGTH);
>> /* Set the length */
>> out_be32 (emaclite.baseaddress + XEL_TPLR_OFFSET,
>> ENET_ADDR_LENGTH);
>> @@ -171,7 +158,7 @@ int eth_init (bd_t * bis)
>> #ifdef CONFIG_XILINX_EMACLITE_TX_PING_PONG
>> /* The same operation with PONG TX */
>> out_be32 (emaclite.baseaddress + XEL_TSR_OFFSET +
>> XEL_BUFFER_OFFSET, 0);
>> - xemaclite_alignedwrite (enetaddr, emaclite.baseaddress +
>> + xemaclite_alignedwrite (dev->enetaddr, emaclite.baseaddress +
>> XEL_BUFFER_OFFSET, ENET_ADDR_LENGTH);
>> out_be32 (emaclite.baseaddress + XEL_TPLR_OFFSET,
>> ENET_ADDR_LENGTH);
> Please consider moving this stuff to a separate function. If you bind
> it to dev->write_hwaddr(), programming will occur at initialization time.
I consider it. This driver is well tested. We are using it for a long time
that's why I prefer to keep it as is. I would look at it when I have free time.
...
>> +
>> +int xilinx_emaclite_initialize (bd_t *bis)
>> +{
>> + struct eth_device *dev;
>> +
>> + dev = malloc(sizeof(*dev));
>> + if (dev == NULL)
>> + hang();
>> +
>> + memset(dev, 0, sizeof(*dev));
>> + sprintf(dev->name, "Xilinx Emaclite");
>> +
>> + dev->iobase = XILINX_EMACLITE_BASEADDR;
> Can you pass this in as a parameter instead? You don't seem to use
> 'bis', so it's not necessary
I did it. version 2 will contain this change.
I am going to send v2. Please review it. I am also sending second patch
with little endian support.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
prev parent reply other threads:[~2010-10-11 1:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 12:49 [U-Boot] [PATCH 1/4] microblaze: Fix microblaze-generic config file Michal Simek
2010-08-02 12:49 ` [U-Boot] [PATCH 2/4] net: Move Emaclite to NET_MULTI Michal Simek
2010-08-02 12:49 ` [U-Boot] [PATCH 3/4] microblaze: Add support for NET_MULTI api Michal Simek
2010-08-02 12:49 ` [U-Boot] [PATCH 4/4] net: Add LL TEMAC driver to u-boot Michal Simek
2010-08-26 12:16 ` Michal Simek
2010-11-28 20:35 ` Wolfgang Denk
2010-12-03 9:33 ` Michal Simek
2010-08-26 12:16 ` [U-Boot] [PATCH 2/4] net: Move Emaclite to NET_MULTI Michal Simek
2010-09-01 5:48 ` Ben Warren
2010-10-11 1:37 ` Michal Simek [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=4CB26A45.7020004@monstr.eu \
--to=monstr@monstr.eu \
--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