linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-fbdev@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v5 0/3] fbdev: Add FOURCC-based format configuration API
Date: Mon, 19 Dec 2011 23:20:48 +0000	[thread overview]
Message-ID: <4EEFC6D0.4070907@gmx.de> (raw)
In-Reply-To: <1323781348-9884-1-git-send-email-laurent.pinchart@ideasonboard.com>

Hi Laurent,

On 12/13/2011 01:02 PM, Laurent Pinchart wrote:
> Hi everybody,
> fbdev: Add FOURCC-based format configuration API
> Here's the fifth version of the fbdev FOURCC-based format configuration API.

Applied this series.


Thanks and congratulations,

Florian Tobias Schandinat

> 
> Compared to the fourth version,
> 
> - fb_set_var() now checks that the red, green, blue and transp fields are all
> set to 0 when using the FOURCC-based API and return an error if they are not
> 
> - the NV24 and NV42 format documentation doesn't include emacs formatting
> directives anymore.
> 
> As usual the fbdev-test tool supporting this new API is available in the
> fbdev-test yuv branch at
> http://git.ideasonboard.org/?pûdev-test.git;a=shortlog;h=refs/heads/yuv.
> 
> Laurent Pinchart (3):
>   fbdev: Add FOURCC-based format configuration API
>   v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats
>   fbdev: sh_mobile_lcdc: Support FOURCC-based format API
> 
>  Documentation/DocBook/media/v4l/pixfmt-nv24.xml |  121 ++++++++
>  Documentation/DocBook/media/v4l/pixfmt.xml      |    1 +
>  Documentation/fb/api.txt                        |  306 +++++++++++++++++++
>  arch/arm/mach-shmobile/board-ag5evm.c           |    2 +-
>  arch/arm/mach-shmobile/board-ap4evb.c           |    4 +-
>  arch/arm/mach-shmobile/board-mackerel.c         |    4 +-
>  arch/sh/boards/mach-ap325rxa/setup.c            |    2 +-
>  arch/sh/boards/mach-ecovec24/setup.c            |    2 +-
>  arch/sh/boards/mach-kfr2r09/setup.c             |    2 +-
>  arch/sh/boards/mach-migor/setup.c               |    4 +-
>  arch/sh/boards/mach-se/7724/setup.c             |    2 +-
>  drivers/video/fbmem.c                           |   14 +
>  drivers/video/sh_mobile_lcdcfb.c                |  360 +++++++++++++++--------
>  include/linux/fb.h                              |   14 +-
>  include/linux/videodev2.h                       |    2 +
>  include/video/sh_mobile_lcdc.h                  |    4 +-
>  16 files changed, 707 insertions(+), 137 deletions(-)
>  create mode 100644 Documentation/DocBook/media/v4l/pixfmt-nv24.xml
>  create mode 100644 Documentation/fb/api.txt
> 


      parent reply	other threads:[~2011-12-19 23:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-13 13:02 [PATCH v5 0/3] fbdev: Add FOURCC-based format configuration API Laurent Pinchart
2011-12-13 13:02 ` [PATCH v5 1/3] " Laurent Pinchart
2011-12-13 13:02 ` [PATCH v5 2/3] v4l: Add V4L2_PIX_FMT_NV24 and V4L2_PIX_FMT_NV42 formats Laurent Pinchart
2011-12-13 13:02 ` [PATCH v5 3/3] fbdev: sh_mobile_lcdc: Support FOURCC-based format API Laurent Pinchart
2011-12-19 23:20 ` Florian Tobias Schandinat [this message]

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=4EEFC6D0.4070907@gmx.de \
    --to=florianschandinat@gmx.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).