Hi,
Here's my second try. I read through the code once more and made some fixes.
Is this correct way to avoid conditional_schedule() when holding spinlock?
Both eepro100 and 3c90x drivers call the command completion wait routine
with spinlock held in few places. I didn't find such situations in 8
Andrew Morton wrote:
>
> As Arjan points out, the eepro100 change will cause deadlocks on SMP,
> and general badness on uniprocessor. But I've done a heap of testing
> on a eepro100 machine and it hasn't been a problem. I expect that
> wait_for_cmd_done() is only a problem during device startup
Jussi Laako wrote:
>
> Hi,
>
> I've done some changes to lowlatency patched kernel. Mainly "fixes" to DRM
> drivers and few network drivers. Most probably I have done something really
> stupid, but those work here(tm). Especially the Radeon driver patch has got
> a lot of testing and seems to ha
On Sat, 12 Jan 2002 23:48:19 +0200
Jussi Laako <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've done some changes to lowlatency patched kernel. Mainly "fixes" to DRM
> drivers and few network drivers. Most probably I have done something really
> stupid, but those work here(tm). Especially the Radeon dr
