[Prism54-devel] [Bug 112] SMC2835W fails with "...your card may be faulty..." in latest cvs

[bugzilla-daemon at mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=112

mathiasb at email.dk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |



------- Additional Comments From mathiasb at email.dk  2005-04-20 07:29 -------
Now, I've first reported this error in october, last year, and at that time    
Margit told me that I could try to do the following, although she didn't    
expect the card to work anyway, as there apparently was an error somewhere in    
my setup, that caused the "your card may be faulty" error:     
    
> If you want to jump over the error, edit islpci_dev.c       
> and comment out lines 526 to 530 -> This :       
>       
>            if (result) {       
>                  printk(KERN_ERR "%s: interface reset failure\n",     
>                  priv->ndev->name);       
>                  up_write(&priv->mib_sem);       
>                  return result;       
>            }      
    
    
So I tried it, and closed the bug. I have been using my card ever since to my    
great satisfaction and, frankly, it is stable as a rock. It is NOT faulty.     
    
So the reason I am reopening this bug is, that I believe that this check is    
not right. Even though the developers think it is necessarry, in my case it is    
not. The card works when the check is not there.    
    
Now, I am not asking that this check should be removed completely, but isn't    
it possible to make an option to the driver to make this check or not? (you    
could call it unsafe_risky_no_check option or whatever so people understand    
that the developers at prism54.org doesn't think they should use their card    
without this check).    
    
I see alot of other bugs and messages where people report having this problem,    
and instead of asking them to uncomment a couple of lines in the driver code    
and recompile the driver (which in cases where you use a system that comes    
with a precompiled kernel image is a rather laborious task), wouldn't it be    
easier to ask them to try and pass an option to the driver, removing that   
check, and see if that gets their card working like mine did?    



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.