public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kelly Huang <kinghuangdk17@gmail.com>
Cc: Felipe Balbi <felipe.balbi@linux.intel.com>,
	linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
	Paul Elder <paul.elder@pitt.edu>
Subject: Re: Some questions about the UVC gadget
Date: Thu, 22 Feb 2018 16:53:13 +0200	[thread overview]
Message-ID: <17074466.0QZEqxoWO3@avalon> (raw)
In-Reply-To: <878tbl75w1.fsf@linux.intel.com>

Hello Kelly,

(CC'ing Paul Elder)

On Thursday, 22 February 2018 11:03:42 EET Felipe Balbi wrote:
> Kelly Huang writes:
> >  Dear Mr.Balbi,
> > 
> > I am a college student from China. Recently, I am doing some research on
> > the UVC gadget. After reading the source code, I found that the uvc gadget
> > framework only supports two types of video streaming format, the
> > UNCOMPRESSED and the MJPEG.
> > 
> > Now, I am trying to add H.264 support. I wonder if the Linux kernel has
> > already support it or not. It will be appreciated if you can give me some
> > advice.
> > 
> > Thank you for your time.
> 
> It's a good idea to add mailing lists and other relevant people to the
> loop.

I'm afraid the Linux UVC gadget driver doesn't support H.264. While H.264 
support could be implemented using UVC 1.1, I wouldn't recommend this as the 
UVC 1.1 H.264 specification is a hack that is not and will not be supported in 
the Linux UVC host driver. UVC 1.5 is the way to go for H.264. This shouldn't 
be too difficult to implement on the gadget side, but the host UVC driver also 
misses UVC 1.5 support.

Paul has recently started working on the UVC gadget driver to revive it along 
with the userspace helper application. Further down on his to-do list he told 
me he would like to implement UVC 1.5 support on the host side, but that won't 
be for the near future (no pressure Paul :-)).

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-02-22 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAEjubf29Ne0XkJoZTqYfbt5xjw2iDw9hsHRuYzCvz9nYJtLpcQ@mail.gmail.com>
2018-02-22  9:03 ` Some questions about the UVC gadget Felipe Balbi
2018-02-22 14:53   ` Laurent Pinchart [this message]
     [not found]     ` <CAEjubf1oP162SEJjF6KgSheeJyvWMH3aSA5hND18Bh4SjQTvTw@mail.gmail.com>
2018-05-21  8:15       ` Laurent Pinchart

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=17074466.0QZEqxoWO3@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=felipe.balbi@linux.intel.com \
    --cc=kinghuangdk17@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=paul.elder@pitt.edu \
    /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