Last time this driver came up the answer was that the userspace was proprietary and this was in fact part of a mixed user/kernel driver which seemed to raise all sorts of interesting questions. This was NAKked before for that reason so why the resubmit. Kernel policy is clear enough ? > + * You need a userspace application to cooperate with this driver. It and > + * more information about this driver can be obtained here: > + * > + * http://wireless.kernel.org/en/users/Drivers/ar5120 Which says: Userspace application This driver requires a userspace application which will interact with the driver via ioctl. More information on this to be posted later. So NAK Let's see an open userspace and then this driver can be submitted + time = wait_event_interruptible_timeout(ar1520_data->wait_irq, + ar1520_data->irq_rx, + msecs_to_jiffies(3142)); Why 3142 ? Come to think of it why not fixes the races while you are it. Alan -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
