All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Warren <biggerbadderben@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] TI: DaVinci DM365: Enabling network Support on DM365 EVM
Date: Tue, 29 Sep 2009 10:05:57 -0700	[thread overview]
Message-ID: <4AC23E75.6070503@gmail.com> (raw)
In-Reply-To: <1254232055-13562-1-git-send-email-s-paulraj@ti.com>

Hi Sandeep,

s-paulraj at ti.com wrote:
> From: Sandeep Paulraj <s-paulraj@ti.com>
>
> This patch enables EMAC on the DM365 EVM.
>
> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
> ---
>   
<snip>
> +	/* Read Ethernet MAC address from EEPROM */
> +	if (dvevm_read_mac_address(eeprom_enetaddr))
> +		dv_configure_mac_address(eeprom_enetaddr);
> +
>   
You should get rid of this function (dv_configure_mac_address), as it 
duplicates logic already present in net/eth.c, albeit in a different 
order.  Mike Frysinger has invested a lot of effort in cleaning this up 
(and documenting it too).  The correct behavior is as follows:

1. davinci_emac_initialize() should read programmed MAC address from ROM 
and stuff it into dev->enetaddr
2. eth_initialize() (in net/eth.c) reads from the environment and 
compares to the value in dev->enetaddr, warning on mismatch.
> +	davinci_emac_initialize();
> +
> +	return 0;
> +}
> +#endif
> +
>  #ifdef CONFIG_NAND_DAVINCI
>  static void nand_dm365evm_select_chip(struct mtd_info *mtd, int chip)
>  {
>   
regards,
Ben

  parent reply	other threads:[~2009-09-29 17:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 13:47 [U-Boot] [PATCH v3] TI: DaVinci DM365: Enabling network Support on DM365 EVM s-paulraj at ti.com
2009-09-29 13:53 ` Tom
2009-09-29 17:05 ` Ben Warren [this message]
2009-09-29 17:39   ` Paulraj, Sandeep

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=4AC23E75.6070503@gmail.com \
    --to=biggerbadderben@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.