Thanks Rob - that approach seems to work.
There still seems to be a problem with the patch, though.
The patch hits three files: iucv.c. iucv.h, and netiucv.c
The first two (iucv.c and iucv.h) apply fine, but the patch to netiucv.c fails to
verify
Here's the first failing hunk from iucv-2.4.17.patch:
@@ -189,7 +192,7 @@
static __inline__ void netiucv_clear_busy(net_device *dev)
{
clear_bit(0, &(((netiucv_priv *)dev->priv)->tbusy));
- netif_start_queue(dev);
+ netif_wake_queue(dev);
}
I applied the following to linux-2.4.17.tar.gz from kernel.org:
+ linux-2.4.17-s390.diff
+ linux-2.4.17-s390-1-lcs.diff
+ linux-2.4.17-s390-2.diff
+ linux-2.4.17-s390-3.diff
This is a code snippet from the resulting netiucv.c:
#if LINUX_VERSION_CODE < 0x02032D
static __inline__ void netiucv_clear_busy(net_device *dev)
{
clear_bit(0 ,(void *)&dev->tbusy);
mark_bh(NET_BH);
}
Clearly, the patch expects to see different parms to clear_bit() and a call to
netif_start_queue
In all, 11 of 22 hunks fail.
Any ideas?
Cheers
Patrick
Patrick A. Carroll
Senior Systems Engineer
L. L. Bean
Casco St
Freeport, ME 04033
(207) 552-2426
[EMAIL PROTECTED]
