Re: [PATCH] change awe_wave initialization to match 2.2 better

2001-02-19 Thread Alan Cox
> It seem obvious that this change in behaviour is isapnptools related, but > not detecting the whole three IO addresses is an unresolved problem (as of > 2.2.18, not tried with built-in PnP support in 2.4.x). Its a bug in the hardware - To unsubscribe from this list: send the line "unsubscribe l

Re: [PATCH] change awe_wave initialization to match 2.2 better

2001-02-19 Thread José Luis Domingo López
On Monday, 19 February 2001, at 14:28:09 -0500, Bill Nottingham wrote: > The awe_wave driver in 2.2 looked at the common I/O ports for > the card if no parameters were specified. The 2.4 driver currently > does an ISAPnP probe, but doesn't fall back to the previous probing > behavior, which means

[PATCH] change awe_wave initialization to match 2.2 better

2001-02-19 Thread Bill Nottingham
The awe_wave driver in 2.2 looked at the common I/O ports for the card if no parameters were specified. The 2.4 driver currently does an ISAPnP probe, but doesn't fall back to the previous probing behavior, which means that users with working module configurations will have theirs broken on upgrad