Re: Marvell driver question

2006-01-23 Thread JaniD++
Hello,

- Original Message - 
From: Stephen Hemminger [EMAIL PROTECTED]
To: JaniD++ [EMAIL PROTECTED]
Cc: netdev@vger.kernel.org
Sent: Thursday, January 12, 2006 10:40 PM
Subject: Re: Marvell driver question


 On Thu, 12 Jan 2006 21:15:21 +0100
 JaniD++ [EMAIL PROTECTED] wrote:

  Hello, list,
 
  I have one problem, with my marvell adapter on my asus motherboard.
  The problem is not exactly with the linux marvell driver, the problem is
  with the marvell-boot-rom. :-)
 
  I want to boot with this card, and the first time it works.
  But after the linux driver gets the card, the next reboot the boot rom
  cannot detect the link. :-)
  The reset did not fix this issue, only the hard poweroff, and wait ~ 1
  minute.
 
  Is there an easy way to workaround this issue?

 Which chip. I suspect the code to power down the driver on remove
 is confusing the boot rom (Windows has the same problem).

 Does this change anything? and what are the initial boot values
 from cold boot and reboot.

init on boot:
skge boot ctst 445
skge addr 0xd7dfc000 irq 22 chip Yukon-Lite rev 9
skge eth0: addr 00:13:d4:5a:f2:b6

The patch did not help. :-(
Sometimes can fetch boot rom the adapter, some times not. (without the patch
the same)
If not, the rom displays link problem, and really the LED shows that too.
If i unplug the cable, and take it back, no change.
Only full power off helps.

The shutdown value is unknown, because i dont know how to log that.
This server boots from this device, and the netconsole using to log with
this device too. :(

(sorry for the late answer, but this is a server, and i dont want to restart
it too often...)

Cheers,
Janos



 --- skge-2.6.orig/drivers/net/skge.c
 +++ skge-2.6/drivers/net/skge.c
 @@ -2993,6 +2993,7 @@ static int skge_reset(struct skge_hw *hw
   int i;

   ctst = skge_read16(hw, B0_CTST);
 + printk(PFX boot ctst %x\n, ctst);

   /* do a SW reset */
   skge_write8(hw, B0_CTST, CS_RST_SET);
 @@ -3355,7 +3356,7 @@ static void __devexit skge_remove(struct
   skge_write32(hw, B0_IMSK, 0);
   skge_write16(hw, B0_LED, LED_STAT_OFF);
   skge_pci_clear(hw);
 - skge_write8(hw, B0_CTST, CS_RST_SET);
 + skge_write8(hw, B0_CTST, CS_MRST_SET);

   tasklet_kill(hw-ext_tasklet);

 -
 To unsubscribe from this list: send the line unsubscribe netdev in
 the body of a message to [EMAIL PROTECTED]
 More majordomo info at  http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: Marvell driver question

2006-01-12 Thread Stephen Hemminger
On Thu, 12 Jan 2006 21:15:21 +0100
JaniD++ [EMAIL PROTECTED] wrote:

 Hello, list,
 
 I have one problem, with my marvell adapter on my asus motherboard.
 The problem is not exactly with the linux marvell driver, the problem is
 with the marvell-boot-rom. :-)
 
 I want to boot with this card, and the first time it works.
 But after the linux driver gets the card, the next reboot the boot rom
 cannot detect the link. :-)
 The reset did not fix this issue, only the hard poweroff, and wait ~ 1
 minute.
 
 Is there an easy way to workaround this issue?

Which chip. I suspect the code to power down the driver on remove
is confusing the boot rom (Windows has the same problem).

Does this change anything? and what are the initial boot values
from cold boot and reboot.

--- skge-2.6.orig/drivers/net/skge.c
+++ skge-2.6/drivers/net/skge.c
@@ -2993,6 +2993,7 @@ static int skge_reset(struct skge_hw *hw
int i;
 
ctst = skge_read16(hw, B0_CTST);
+   printk(PFX boot ctst %x\n, ctst);
 
/* do a SW reset */
skge_write8(hw, B0_CTST, CS_RST_SET);
@@ -3355,7 +3356,7 @@ static void __devexit skge_remove(struct
skge_write32(hw, B0_IMSK, 0);
skge_write16(hw, B0_LED, LED_STAT_OFF);
skge_pci_clear(hw);
-   skge_write8(hw, B0_CTST, CS_RST_SET);
+   skge_write8(hw, B0_CTST, CS_MRST_SET);
 
tasklet_kill(hw-ext_tasklet);
 
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html