netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: john.ronciak@intel.com, jesse.brandeburg@intel.com,
	netdev@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] Rewrite e100_phys_id
Date: Tue, 7 Nov 2006 12:06:32 -0700	[thread overview]
Message-ID: <20061107190632.GW27140@parisc-linux.org> (raw)
In-Reply-To: <4550D16A.1090008@intel.com>

On Tue, Nov 07, 2006 at 10:33:14AM -0800, Auke Kok wrote:
> Matthew Wilcox wrote:
> >Tested on the internal interface of an HP Integrity rx2600.
> 
> bad news, it's completely hosed. The adapter does some indistinguishable 
> blinking for a second, then stops blinking alltogether.

Weird.  I tested it on the only e100 I have access to, and it worked.
I've just reviewed the patch you quoted below, and I don't see what the
problem is.  

I wonder if this is wrong:

> >-    mdio_write(netdev, nic->mii.phy_id, MII_LED_CONTROL, 0);
> >+    mdio_write(netdev, nic->mii.phy_id, MII_LED_CONTROL, led_off);

but everything else seems pretty straight-forward.

> I might revert the code to the old situation. I guess I should have tested 
> it initially right away.
> 
> I'm not even going to touch the e1000 patch for now ;)
> 
> Auke
> 
> >
> >Signed-off-by: Matthew Wilcox <matthew@wil.cx>
> >
> >diff --git a/drivers/net/e100.c b/drivers/net/e100.c
> >index a3a08a5..aade1e9 100644
> >--- a/drivers/net/e100.c
> >+++ b/drivers/net/e100.c
> >@@ -556,7 +556,6 @@ struct nic {
> > 	struct params params;
> > 	struct net_device_stats net_stats;
> > 	struct timer_list watchdog;
> >-	struct timer_list blink_timer;
> > 	struct mii_if_info mii;
> > 	struct work_struct tx_timeout_task;
> > 	enum loopback loopback;
> >@@ -581,7 +580,6 @@ struct nic {
> > 	u32 rx_over_length_errors;
> > 
> > 	u8 rev_id;
> >-	u16 leds;
> > 	u16 eeprom_wc;
> > 	u16 eeprom[256];
> > 	spinlock_t mdio_lock;
> >@@ -2168,23 +2166,6 @@ err_clean_rx:
> > 	return err;
> > }
> > 
> >-#define MII_LED_CONTROL	0x1B
> >-static void e100_blink_led(unsigned long data)
> >-{
> >-	struct nic *nic = (struct nic *)data;
> >-	enum led_state {
> >-		led_on     = 0x01,
> >-		led_off    = 0x04,
> >-		led_on_559 = 0x05,
> >-		led_on_557 = 0x07,
> >-	};
> >-
> >-	nic->leds = (nic->leds & led_on) ? led_off :
> >-		(nic->mac < mac_82559_D101M) ? led_on_557 : led_on_559;
> >-	mdio_write(nic->netdev, nic->mii.phy_id, MII_LED_CONTROL, nic->leds);
> >-	mod_timer(&nic->blink_timer, jiffies + HZ / 4);
> >-}
> >-
> > static int e100_get_settings(struct net_device *netdev, struct 
> > ethtool_cmd *cmd)
> > {
> > 	struct nic *nic = netdev_priv(netdev);
> >@@ -2411,16 +2392,32 @@ static void e100_diag_test(struct net_de
> > 	msleep_interruptible(4 * 1000);
> > }
> > 
> >+#define MII_LED_CONTROL	0x1B
> > static int e100_phys_id(struct net_device *netdev, u32 data)
> > {
> > 	struct nic *nic = netdev_priv(netdev);
> >+	int i;
> >+
> >+	enum led_state {
> >+		led_off    = 0x04,
> >+		led_on_559 = 0x05,
> >+		led_on_557 = 0x07,
> >+	};
> >+	u16 leds = led_off;
> >+
> >+	if (data == 0)
> >+		data = 2;
> >+
> >+	for (i = 0; i < (data * 2); i++) {
> >+		leds = (leds == led_off) ?
> >+			(nic->mac < mac_82559_D101M) ? led_on_557 : 
> >led_on_559 :
> >+			led_off;
> >+		mdio_write(nic->netdev, nic->mii.phy_id, MII_LED_CONTROL, 
> >leds);
> >+		if (msleep_interruptible(500))
> >+			break;
> >+	}
> > 
> >-	if(!data || data > (u32)(MAX_SCHEDULE_TIMEOUT / HZ))
> >-		data = (u32)(MAX_SCHEDULE_TIMEOUT / HZ);
> >-	mod_timer(&nic->blink_timer, jiffies);
> >-	msleep_interruptible(data * 1000);
> >-	del_timer_sync(&nic->blink_timer);
> >-	mdio_write(netdev, nic->mii.phy_id, MII_LED_CONTROL, 0);
> >+	mdio_write(netdev, nic->mii.phy_id, MII_LED_CONTROL, led_off);
> > 
> > 	return 0;
> > }
> >@@ -2633,9 +2630,6 @@ #endif
> > 	init_timer(&nic->watchdog);
> > 	nic->watchdog.function = e100_watchdog;
> > 	nic->watchdog.data = (unsigned long)nic;
> >-	init_timer(&nic->blink_timer);
> >-	nic->blink_timer.function = e100_blink_led;
> >-	nic->blink_timer.data = (unsigned long)nic;
> > 
> > 	INIT_WORK(&nic->tx_timeout_task,
> > 		(void (*)(void *))e100_tx_timeout_task, netdev);

  reply	other threads:[~2006-11-07 19:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26 19:11 [PATCH] Rewrite e100_phys_id Matthew Wilcox
2006-10-26 19:19 ` Jeff Garzik
2006-10-26 20:04   ` Auke Kok
2006-10-27  2:51     ` Matthew Wilcox
2006-10-27 14:44       ` Auke Kok
2006-11-07 18:33 ` Auke Kok
2006-11-07 19:06   ` Matthew Wilcox [this message]
2006-11-07 22:34     ` Auke Kok

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=20061107190632.GW27140@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=auke-jan.h.kok@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=jgarzik@pobox.com \
    --cc=john.ronciak@intel.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).