Hi, Some documentation on the subject: http://www.quickcamteam.net/uvc-h264
Regards, Paulo 2011/6/16 Ajay Bhargav <ajay.bhar...@einfochips.com>: > Hi Alexey, > > Thanks for reply, Well i have already done this before even i saw that > patches in mailing list... I am able to add /dev/video0 device on my machine > but i am not able to read from that device. Here is the log: > > > uvcvideo 1-1.2:1.0: usb_probe_interface > uvcvideo 1-1.2:1.0: usb_probe_interface - got id > uvcvideo: Probing generic UVC device 1.2 > uvcvideo: Videostreaming interface: 0x0A > uvcvideo: Format 10, Desc Size: 7 > uvcvideo: Found format MPEG2-TS. > uvcvideo: Found a Status endpoint (addr 81). > uvcvideo: Found UVC 1.00 device USB Camera Aoni (04a8:0536) > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/2 to device 1.2 > entity 5 > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/3 to device 1.2 > entity 5 > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/6 to device 1.2 > entity 5 > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/7 to device 1.2 > entity 5 > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/8 to device 1.2 > entity 5 > uvcvideo: Added control 00000000-0000-0000-0000-000000000101/5 to device 1.2 > entity 5 > uvcvideo: Scanning UVC chain: OT 3 <- PU 5 <- SU 4 <- IT 1 > (-> XU 6)<6>uvcvideo: video stream id: 3 > uvcvideo: Stream List id: 3, Dev stream id: 3 > uvcvideo: Found a valid video chain (1 -> 3). > uvcvideo: UVC non compliance - GET_DEF(PROBE) not supported. Enabling > workaround. > input: USB Camera Aoni as /class/input/input0 > usb 1-1.2: link qh1024-0001/ff389200 start 1023 [1/0 us] > uvcvideo: UVC device initialized. > usb 1-1.2: adding 1-1.2:1.1 (config #1, interface 1) > usb 1-1.2:1.1: uevent > usb 1-1.2: adding 1-1.2:1.2 (config #1, interface 2) > usb 1-1.2:1.2: uevent > snd-usb-audio 1-1.2:1.2: usb_probe_interface > snd-usb-audio 1-1.2:1.2: usb_probe_interface - got id > usb 1-1.2: adding 1-1.2:1.3 (config #1, interface 3) > usb 1-1.2:1.3: uevent > uvcvideo: uvc_v4l2_open > uvcvideo: uvc_v4l2_ioctl(VIDIOC_QUERYCAP) > uvcvideo: uvc_v4l2_ioctl(VIDIOCGCAP) > uvcvideo: Trying format 0x4745504d (MPEG): 10000x10000. > uvcvideo: Default cam size: 10000x10000. > uvcvideo: Using default frame interval 0.1 us (10000000.0 fps). > uvcvideo: uvc_v4l2_release > > As per this conversation > (http://lists.berlios.de/pipermail/linux-uvc-devel/2009-July/005008.html) it > looks like there are lot more changes to be done, so that UVC is able to > forward proper information to v4l2 layer. > > --Ajay > > > ----- Original Message ----- > From: "Alexey Fisher" <bug-tr...@fisher-privat.net> > To: "Ajay Bhargav" <ajay.bhar...@einfochips.com> > Cc: linux-uvc-devel@lists.berlios.de, "Kofi Jedamzik" <k...@jedamzik.net> > Sent: Thursday, June 16, 2011 12:06:02 PM > Subject: Re: [Linux-uvc-devel] Webcam with H264 encoder not in Devicelist > > Hi, > > Stephan Lachowsky has provided some patches for MPEG-TS and H264 > support. > https://lists.berlios.de/pipermail/linux-uvc-devel/2011-February/006287.html > https://lists.berlios.de/pipermail/linux-uvc-devel/2011-February/006288.html > > I do not know the current status of this work. May be Laurent can tell > some thing about it. > > Am Donnerstag, den 16.06.2011, 10:26 +0530 schrieb Ajay Bhargav: >> Hi, >> >> as far as i know stream based format are not yet supported in UVC >> driver. and UVC 1.1 specifications defines the H.264 payload >> specifications. I dont think they are implemented yet. >> >> I have a camera with me which outputs H.264 stream using MPEG2-TS >> container format. If you have any idea how to add support for MPEG2-TS >> please let me know. >> >> --Ajay >> >> ----- Original Message ----- >> From: "Alexey Fisher" <bug-tr...@fisher-privat.net> >> To: "Kofi Jedamzik" <k...@jedamzik.net> >> Cc: linux-uvc-devel@lists.berlios.de >> Sent: Wednesday, June 15, 2011 8:10:36 PM >> Subject: Re: [Linux-uvc-devel] Webcam with H264 encoder not in >> Devicelist >> >> Hi, >> >> theoretically this should do it: >> gst-inspect-0.10 v4l2src ! video/x-h264 ! ffdec_h264 ! autovideosink >> >> but, if i'm correct, current kernel do not support h264. There was a >> patch for some time, but im not sure if Laurent applyed it. >> >> Am Mittwoch, den 15.06.2011, 16:01 +0200 schrieb Kofi Jedamzik: >> > Hi, >> > >> > ... there is a "new" Logitech Webcam called "B990 HD Webcam" with >> > device id 046d:0828 >> > it has an integrated hardware based H264 baseline video encoder >> > >> > This cam is not listed. >> > >> > MJPEG seems to work but I want to get out the H264 stream. >> > >> > Is there anyone who could give me a hint how to do it? >> > >> > Here are som dumps which might be helpful... >> > >> > best regards >> > >> > Kofi >> > >> > #lsusb --verbose -d 046d:0828 >> > (big output) -->> http://pastebin.com/9WFgytwY >> > >> > #guvcview --device /dev/video0 --verbose >> > (big output) -->> http://pastebin.com/pqmUGYyn >> > >> > #modinfo uvcvideo >> > filename: >> > /lib/modules/2.6.38-8-generic/kernel/drivers/media/video/uvc/uvcvideo.ko >> > version: v1.0.0 >> > >> > #tail /var/log/syslog >> > [11588.664940] usb 1-6: USB disconnect, address 4 >> > [11594.580043] usb 1-6: new high speed USB device using ehci_hcd and >> address 5 >> > [11594.927759] uvcvideo: Unknown video format >> > 34363248-0000-0010-8000-00aa00389b71 >> > [11594.927786] uvcvideo: Found UVC 1.00 device <unnamed> (046d:0828) >> > [11595.024093] input: UVC Camera (046d:0828) as >> > /devices/pci0000:00/0000:00:12.2/usb1/1-6/1-6:1.0/input/input8 >> -- >> Regards, >> Alexey >> >> _______________________________________________ >> Linux-uvc-devel mailing list >> Linux-uvc-devel@lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/linux-uvc-devel >> >> -- >> This message has been scanned for viruses and >> dangerous content by Clean Mail Gateway, and is >> believed to be clean. >> >> >> ************************************************************************************************************************************************************* >> einfochips Business Disclaimer : This e-mail message and all >> attachments transmitted with it are intended solely for the use of the >> addressee and may contain legally privileged and confidential >> information. If the reader of this message is not the intended >> recipient, or an employee or agent responsible for delivering this >> message to the intended recipient, you are hereby notified that any >> dissemination, distribution, copying, or other use of this message or >> its attachments is strictly prohibited. If you have received this >> message in error, please notify the sender immediately by replying to >> this message and please delete it from your computer. Any views >> expressed in this message are those of the individual sender unless >> otherwise stated. Company has taken enough precautions to prevent the >> spread of viruses. However the company accepts no liability for any >> damage caused by any virus transmitted by this email. >> >> ************************************************************************************************************************************************************* >> >> > > -- > Regards, > Alexey > > > -- > This message has been scanned for viruses and > dangerous content by Clean Mail Gateway, and is > believed to be clean. > > ************************************************************************************************************************************************************* > einfochips Business Disclaimer : This e-mail message and all attachments > transmitted with it are intended solely for the use of the addressee and may > contain legally privileged and confidential information. If the reader of > this message is not the intended recipient, or an employee or agent > responsible for delivering this message to the intended recipient, you are > hereby notified that any dissemination, distribution, copying, or other use > of this message or its attachments is strictly prohibited. If you have > received this message in error, please notify the sender immediately by > replying to this message and please delete it from your computer. Any views > expressed in this message are those of the individual sender unless > otherwise stated. Company has taken enough precautions to prevent the spread > of viruses. However the company accepts no liability for any damage caused > by any virus transmitted by this email. > ************************************************************************************************************************************************************* > > > _______________________________________________ > Linux-uvc-devel mailing list > Linux-uvc-devel@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/linux-uvc-devel > > _______________________________________________ Linux-uvc-devel mailing list Linux-uvc-devel@lists.berlios.de https://lists.berlios.de/mailman/listinfo/linux-uvc-devel
