Resolved: ISAPNP BUG: 2.4.65 ne2000 driver w. isapnp not working

[Michael Frank <mflt1@micrologica.com.hk>]

Martin,

Thank you for getting the fix going and sending me this patch which I applid on 2.5.66.

The problem is resolved:

  .config: CONFIG_NE2000=m

  Tested:
    network start on boot: 		OK
    several network restart:		OK
    rmmod ne 8390; network start:	OK
    several network restart:		OK

I like also to thank Adam Belay for getting this fixed.


Best Regards
Michael

 

On Wednesday 26 March 2003 21:01, you wrote:
> Michael,
>
> Adam Belay has posted some PNP patches you may want to try for 2.5.66.
>
> One of them looks like it may help...I haven't tried.
>
> Martin
>
>
>
> diff -Nru a/drivers/pnp/manager.c b/drivers/pnp/manager.c
> --- a/drivers/pnp/manager.c Tue Mar 25 21:44:41 2003
> +++ b/drivers/pnp/manager.c Tue Mar 25 21:44:41 2003
> @@ -632,8 +632,7 @@
>          if (!dev)
>                  return -EINVAL;
>          if (dev->active) {
> - pnp_info("res: The PnP device '%s' is already active.", dev->dev.bus_id);
> - return -EBUSY;
> + return 0; /* the device is already active */
>          }
>          /* If this condition is true, advanced configuration failed, we
> need to get this device up and running * so we use the simple config engine
> which ignores cold conflicts, this of course may lead to new failures */ @@
> -698,8 +697,7 @@
>          if (!dev)
>                  return -EINVAL;
>          if (!dev->active) {
> - pnp_info("res: The PnP device '%s' is already disabled.",
> dev->dev.bus_id); - return -EINVAL;
> + return 0; /* the device is already disabled */
>          }
>          if (dev->status != PNP_READY){
>                  pnp_info("res: Disable failed becuase the PnP device '%s'
> is busy.", dev->dev.bus_id);