Hi,
Why not send these fixes to the upstream developers so you do not have to constantly rebuild things for new kernels? That's the best way to resolve this issue. I would hardly call these fixes. We just a find a way to vanish/handle our problem. However what we are unsure about is whether our fixes "fine" enough (i.e. they integrate into the kernel infrastructure "well"), or is there any other way to do it better (that is why I was thinking about the USBDEVFS_RESET ioctl()).
Oh, and it sounds like you should really fix your printer's firmware, it seems quite broken.
Sadly I can't agree on that, as it happens "rarely" (naturally because of that ONLY it could well be a firmware issue) and definetely not all printers are affected (talking about cca. ten-thousand deployed Uniboard printers overall, and talking about a few (below 100) "failing" pieces, and naturally swapping printers do not help, so it is hard to blame the printer itself only, it might be that we have a kind of "disturbance in the force" somewhere). Thanks, Tibor -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org