From: Ben Warren <biggerbadderben@gmail.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: Wed, 03 Sep 2008 23:00:18 -0700 [thread overview]
Message-ID: <48BF7972.3020905@gmail.com> (raw)
In-Reply-To: <48A9D30D.5020008@ruggedcom.com>
Hi Richard,
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.
>
>
My general issue with this patch is that if this functionality is really
useful, it should be in the main device control flow (net/eth.c), not in
a single driver.
> Signed-off-by: Richard Retanubun <RichardRetanubun_at_ruggedcom.com>
>
> diff --git a/drivers/qe/uec.c b/drivers/qe/uec.c
> index 344c649..88402ca 100644
> --- a/drivers/qe/uec.c
> +++ b/drivers/qe/uec.c
> @@ -1192,9 +1192,17 @@ static int uec_init(struct eth_device* dev, bd_t *bd)
> uec_private_t *uec;
> int err, i;
> struct phy_info *curphy;
> + char *netretry = NULL;
>
> uec = (uec_private_t *)dev->priv;
>
> +
> + /* Allow for net re-initialization based on netretry environment
> setting */
> + netretry = getenv("netretry");
> + if (netretry != NULL && (strcmp(netretry, "yes") == 0)) {
> + uec->the_first_run = 0;
> + }
> +
>
I'm sure you know that "netretry" already exists, and has a different
meaning. It's not a good idea for an environment variable to do
different things depending on context.
> if (uec->the_first_run == 0) {
> err = init_phy(dev);
> if (err) {
> @@ -1223,12 +1231,16 @@ static int uec_init(struct eth_device* dev, bd_t
> *bd)
> if (err || i <= 0)
> printf("warning: %s: timeout on PHY link\n", dev->name);
>
> - uec->the_first_run = 1;
> + /* If netretry is not set, or not set to yes, assume no retry */
> + netretry = getenv("netretry");
> + if (netretry == NULL || (strcmp(netretry, "yes") != 0)) {
> + uec->the_first_run = 1;
> + }
> }
>
> /* Set up the MAC address */
> if (dev->enetaddr[0] & 0x01) {
> - printf("%s: MacAddress is multcast address\n",
> + printf("%s: MacAddress is multicast address\n",
> __FUNCTION__);
>
OK, good catch.
Sorry again for taking so long to respond properly.
regards,
Ben
next prev parent reply other threads:[~2008-09-04 6:00 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
2008-09-04 6:00 ` Ben Warren [this message]
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=48BF7972.3020905@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox