All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Klimov <klimov.linux@gmail.com>
To: Vladimir Davydov <vladimir.davydov@promwad.com>
Cc: "video4linux-list@redhat.com" <video4linux-list@redhat.com>,
	linux-media@vger.kernel.org
Subject: Re: Request for new pixel format (JPEG2000)
Date: Thu, 22 Jan 2009 08:09:02 +0300	[thread overview]
Message-ID: <1232600942.3764.130.camel@tux.localhost> (raw)
In-Reply-To: <200901212146.39153.vladimir.davydov@promwad.com>

(added linux-media mail-list)

Hello, Vladimir

On Wed, 2009-01-21 at 21:46 +0200, Vladimir Davydov wrote:
> Hi,
> Is it possible to add new pixel format to videodev2.h file?
> 
> #define V4L2_PIX_FMT_MJ2C   v4l2_fourcc('M','J','2','C') /* Morgan JPEG 2000*/
> 
> I have developed a V4L2 driver for the board with hardware JPEG2000 codec 
> (ADV202 chip). This driver uses that pixel format.
> I think JPEG 2000 is very perspective codec and it will be good if V4L2 will 
> support it.
> 
> Short description of the device is here:
> http://www.promwad.com/markets/linux-video-jpeg2000-blackfin.html
> 
> Thanks,
> Vladimir.

Please, send patches and other e-mails related to drivers development to
linux-media@vger.kernel.org
Such tool like patchwork.kernel.org will cares about patches, so they
don't lost. 

I think you already check this page
http://linuxtv.org/wiki/index.php/Development:_How_to_submit_patches
if not, please check.

-- 
Best regards, Klimov Alexey


  reply	other threads:[~2009-01-22  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 19:46 Request for new pixel format (JPEG2000) Vladimir Davydov
2009-01-22  5:09 ` Alexey Klimov [this message]
2009-01-22  7:19   ` Hans Verkuil
2009-01-22 10:03     ` Vladimir Davydov
2009-01-22 19:37       ` Mauro Carvalho Chehab
2009-01-22 20:40         ` Vladimir Davydov

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=1232600942.3764.130.camel@tux.localhost \
    --to=klimov.linux@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=video4linux-list@redhat.com \
    --cc=vladimir.davydov@promwad.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.