On Mon, Sep 12, 2011 at 1:33 PM, Greg KH <greg@xxxxxxxxx> wrote: > On Mon, Sep 12, 2011 at 12:18:02PM +0200, Markus Rechberger wrote: >> Hi, >> >> I'm a little bit curious why you guys are just ignoring this. > > Because you seem to be ignoring the fact that changing this can cause > problems on systems. > Can you explain which problems? We are even using analogTV on Freescale ARM Systems. There is no way to read the maximum allowed buffersize from the kernel right now, if an application wants to use it they roughly need to know the current maximum packet size. Since this is about a product I'm not eager to introduce trouble to our customers frankly speaking those things are well tested at our side. > And because it really doesn't solve any problems, wrong, it does solve problems, and it also solved it in the past for isochronous. Would it help if we ship a sample device to you? The easiest way to reproduce this is to take 2 different Ubuntu versions, an old one with lower Isochronous packet size eg. Ubuntu 9.04 and another new one Ubuntu 10.04. Simply dragging the player with Ubuntu 9.04 can cause framedrops, while it works smoothly with 10.04. Next step update the buffer with 9.04 and the video is also smoothly with the old version - and there are no framedrops (=incomplete data). I can imagine because the application just gets a certain timeslice and cannot reliable requeue many packets. The problem with Bulk is that we need to submit many Bulk URBs in order to get it work at all, aside of that it shows up the same issue as with isochronous. > you are only pushing > the processing to the kernel, when it can be done in userspace just as > easily. > Your assumption is wrong, even though I understand your point. All I want is to sort this out. Markus -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
