Gitweb:     
http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=991b5557f7f04602b3b161341dee85971e0b6be6
Commit:     991b5557f7f04602b3b161341dee85971e0b6be6
Parent:     604119a4b22b95e30dea6af3b3bfdc2f07fa4afd
Author:     Jeff Garzik <[EMAIL PROTECTED]>
AuthorDate: Fri Mar 23 02:03:29 2007 -0400
Committer:  Jeff Garzik <[EMAIL PROTECTED]>
CommitDate: Fri Mar 23 02:03:29 2007 -0400

    [netdrvr] ewrk3: correct card detection bug
    
    Arwin Vosselman pointed out:
    > The ewrk3-driver doesn't function with 2.6.16-kernels (used 2.6.16.41 for
    > my tests). Cards will never be detected due to this bug.
    >
    > drivers/net/ewrks3.c:
    > Line 417 reads:
    >
    > if (nicsr == (CSR_TXD | CSR_RXD))
    >
    > that should be:
    >
    > if (nicsr != (CSR_TXD | CSR_RXD))
    >
    > Comparison with the same line in v2.4 shows why:
    >
    > 2.4:
    > if (nicsr == (CSR_TXD | CSR_RXD)){
    >
    > blah, blah
    > ==========
    > 2.6:
    > if (nicsr == (CSR_TXD | CSR_RXD))
    >     return -ENXIO;
    >
    > blah, blah
    > ==========
    >
    > blah,blah will not, but should, be executed in 2.6 with a card being 
present.
    >
    > The fix mentioned above solves this bug.
    
    Signed-off-by: Jeff Garzik <[EMAIL PROTECTED]>
---
 drivers/net/ewrk3.c |    3 +--
 1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ewrk3.c b/drivers/net/ewrk3.c
index c8c41f0..714ea11 100644
--- a/drivers/net/ewrk3.c
+++ b/drivers/net/ewrk3.c
@@ -414,10 +414,9 @@ ewrk3_hw_init(struct net_device *dev, u_long iobase)
        icr &= 0x70;
        outb(icr, EWRK3_ICR);   /* Disable all the IRQs */
 
-       if (nicsr == (CSR_TXD | CSR_RXD))
+       if (nicsr != (CSR_TXD | CSR_RXD))
                return -ENXIO;
 
-
        /* Check that the EEPROM is alive and well and not living on Pluto... */
        for (chksum = 0, i = 0; i < EEPROM_MAX; i += 2) {
                union {
-
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to