public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: richardretanubun <richardretanubun@ruggedcom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-boot] [PATCH 2/2] NET: QE: UEC: Allow uec re-initialization based on netretry environment variable.
Date: Mon, 18 Aug 2008 19:03:17 -0400	[thread overview]
Message-ID: <48A9FFB5.4020303@ruggedcom.com> (raw)
In-Reply-To: <48A9E6E4.8070707@gmail.com>

Hi Ben,

Ben Warren wrote:
> richardretanubun wrote:
>> Allow uec_init to run more than once, based on the netretry 
>> environment variable.
>> This allows for manual (back and forth) switching between network 
>> interfaces.
>>
>>   
> Can't you do this by changing the 'ethactive' environment variable?
You are correct,  changing 'ethact' environment variable works if you 
are actually changing the network interface (say from "FSL UEC0" to "FSL 
UEC1")

I'm sorry for not adding this earlier.

The scenario I am trying to handle is if switching network interface fails.
I am trying to switch and activate specific network interfaces for 
testing and
often times the interface will fail to initialize and will have to be 
reinitialized

I am using these function call sequence to do activate the specific eth 
interface repeatedly:

void net_set_eth(char *newEthDev)
{
    ....
    setenv("ethact", newEthDev);
    eth_set_current();
    eth_init(gd->bd);
    ....
}

By adding the patch, I can just keep trying the same eth interface. The 
'ethrotate' environment variable will also work,
but only for rotating once, once a failure occur, there is no way to 
retry the same ethernet connection.

>
> regards,
> Ben

Hope this does not confuse more :)

- Richard.

  reply	other threads:[~2008-08-18 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18 19:52 [U-Boot] [U-boot] [PATCH 2/2] NET: QE: UEC: Allow uec re-initialization based on netretry environment variable richardretanubun
2008-08-18 21:17 ` Ben Warren
2008-08-18 23:03   ` richardretanubun [this message]
2008-09-04  6:00 ` Ben Warren
2008-09-16 13:10   ` richardretanubun

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=48A9FFB5.4020303@ruggedcom.com \
    --to=richardretanubun@ruggedcom.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