From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Pierre ANTOINE <nunux@free.fr>
Cc: linux-media@vger.kernel.org
Subject: Re: uvcvideo: Trying to lower the URB buffers on eMPIA minicam
Date: Fri, 26 Apr 2013 02:41:58 +0200 [thread overview]
Message-ID: <1880069.7yVprJ14P8@avalon> (raw)
In-Reply-To: <1366934628.5179c4650033f@imp.free.fr>
Hi Pierre,
On Friday 26 April 2013 02:03:49 Pierre ANTOINE wrote:
> Selon Laurent Pinchart <laurent.pinchart@ideasonboard.com>:
> > Thank you. I'll update the supported devices list on the uvcvideo website.
> > Could you please give me the exact model name of the camera ?
>
> The product description is here:
>
> http://www.amazon.fr/dp/B00A487TPC/ref=pe_205631_30430471_3p_M3_dp_1
>
> That is: Supereyes from XCSource know on Amazon as Microscope USB Cam.
Thank you.
> > Yes, that looks good. Just make sure you only hack the endpoint bandwidth
> > for the webcam and not for the other USB devices.
>
> I'm trying this one:
>
> ---------------------------------------
> if (to_usb_device(ddev)->speed == USB_SPEED_HIGH)
> {
> unsigned maxp;
>
> maxp = usb_endpoint_maxp(&endpoint->desc) & 0x07ff;
> if (maxp == 912) endpoint->desc.wMaxPacketSize =
> cpu_to_le16(256);
> dev_warn(ddev, "Hack 912 to 256 downsize endpoint by
> Nunux"); }
> ---------------------------------------
>
> That seem to trigger ... but not working ... and not showing is lsusb ...
lsusb parses the raw descriptors. Could you print the wMaxPacketSize value for
all the endpoints in the uvcvideo driver ? The value is also exported through
a sysfs attribute.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-04-26 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 22:47 uvcvideo: Trying to lower the URB buffers on eMPIA minicam Pierre ANTOINE
2013-04-25 11:36 ` Laurent Pinchart
2013-04-25 19:13 ` Pierre ANTOINE
2013-04-25 22:55 ` Laurent Pinchart
2013-04-26 0:03 ` Pierre ANTOINE
2013-04-26 0:41 ` Laurent Pinchart [this message]
2013-04-26 0:56 ` Pierre ANTOINE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1880069.7yVprJ14P8@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=nunux@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox