The patch titled
     sundance: PHY address form 0, only for device ID 0x0200 (IP100A) (20070605)
has been added to the -mm tree.  Its filename is
     sundance-phy-address-form-0-only-for-device-id-0x0200.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: sundance: PHY address form 0, only for device ID 0x0200 (IP100A) 
(20070605)
From: Jesse Huang <[EMAIL PROTECTED]>

Search PHY address form 0, only for device ID 0x0200 (IP100A).  Other
device are from PHY address 1.

Signed-off-by: Jesse Huang <[EMAIL PROTECTED]>
Cc: Jeff Garzik <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 drivers/net/sundance.c |    6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff -puN 
drivers/net/sundance.c~sundance-phy-address-form-0-only-for-device-id-0x0200 
drivers/net/sundance.c
--- 
a/drivers/net/sundance.c~sundance-phy-address-form-0-only-for-device-id-0x0200
+++ a/drivers/net/sundance.c
@@ -562,7 +562,11 @@ static int __devinit sundance_probe1 (st
         * It seems some phys doesn't deal well with address 0 being accessed
         * first, so leave address zero to the end of the loop (32 & 31).
         */
-       for (phy = 1; phy <= 32 && phy_idx < MII_CNT; phy++) {
+       if(sundance_pci_tbl[np->chip_id].device == 0x0200)
+               phy = 0;
+       else
+               phy = 1;
+       for (; phy <= 32 && phy_idx < MII_CNT; phy++) {
                int phyx = phy & 0x1f;
                int mii_status = mdio_read(dev, phyx, MII_BMSR);
                if (mii_status != 0xffff  &&  mii_status != 0x0000) {
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

sundance-phy-address-form-0-only-for-device-id-0x0200.patch
sundance-phy-address-form-0-only-for-device-id-0x0200-fix.patch

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

Reply via email to