All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: bryan.wu@analog.com
Cc: uclinux-dist-devel@blackfin.uclinux.org,
	linux-fbdev-devel@lists.sourceforge.net,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer	device driver for a SHARP LQ043T1DG01 TFT LCD
Date: Sat, 29 Sep 2007 08:09:30 +0800	[thread overview]
Message-ID: <1191024570.5273.4.camel@daplas> (raw)
In-Reply-To: <1190778219.18676.13.camel@roc-laptop>

On Wed, 2007-09-26 at 11:43 +0800, Bryan Wu wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
> Date: Wed, 26 Sep 2007 11:33:01 +0800
> Subject: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
> 
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> ---
>  drivers/video/Kconfig                         |    9 +
>  drivers/video/Makefile                        |    1 +
>  drivers/video/bf54x-lq043.c                   |  786 +++++++++++++++++++++++++
>  include/asm-blackfin/mach-bf548/bf54x-lq043.h |   30 +
>  4 files changed, 826 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/video/bf54x-lq043.c
>  create mode 100644 include/asm-blackfin/mach-bf548/bf54x-lq043.h
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 5216c11..41fae00 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -535,6 +535,15 @@ config FB_VGA16
>  	  To compile this driver as a module, choose M here: the
>  	  module will be called vga16fb.
>  
> +config FB_BF54X_LQ043
> +	tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
> +	depends on FB && (BF54x)
> +	select FB_CFB_FILLRECT
> +	select FB_CFB_COPYAREA
> +	select FB_CFB_IMAGEBLIT
> +	help
> +	 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
> +
>  config FB_STI
>  	tristate "HP STI frame buffer device support"
>  	depends on FB && PARISC
> diff --git a/drivers/video/Makefile b/drivers/video/Makefile
> index 06eec7b..359e560 100644
> --- a/drivers/video/Makefile
> +++ b/drivers/video/Makefile
> @@ -122,6 +122,7 @@ obj-$(CONFIG_FB_OF)               += offb.o
>  
>  # the test framebuffer is last
>  obj-$(CONFIG_FB_VIRTUAL)          += vfb.o
> +obj-$(CONFIG_FB_BF54X_LQ043)	  += bf54x-lq043.o

It's standard that we suffix all framebuffer drivers with an 'fb'. I'm
making it so in my tree.

Also, you shouldn't place your driver after vfb, that's why there's a
comment that the test framebuffer is last. If someone accidentally
enables vfb, he/she will get a blank screen. So I'm moving it under the
platform driver section. 

Tony




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

WARNING: multiple messages have this Message-ID (diff)
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: bryan.wu@analog.com
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Michael Hennerich <michael.hennerich@analog.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
Date: Sat, 29 Sep 2007 08:09:30 +0800	[thread overview]
Message-ID: <1191024570.5273.4.camel@daplas> (raw)
In-Reply-To: <1190778219.18676.13.camel@roc-laptop>

On Wed, 2007-09-26 at 11:43 +0800, Bryan Wu wrote:
> From: Michael Hennerich <michael.hennerich@analog.com>
> Date: Wed, 26 Sep 2007 11:33:01 +0800
> Subject: [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
> 
> Signed-off-by: Michael Hennerich <michael.hennerich@analog.com>
> Signed-off-by: Bryan Wu <bryan.wu@analog.com>
> ---
>  drivers/video/Kconfig                         |    9 +
>  drivers/video/Makefile                        |    1 +
>  drivers/video/bf54x-lq043.c                   |  786 +++++++++++++++++++++++++
>  include/asm-blackfin/mach-bf548/bf54x-lq043.h |   30 +
>  4 files changed, 826 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/video/bf54x-lq043.c
>  create mode 100644 include/asm-blackfin/mach-bf548/bf54x-lq043.h
> 
> diff --git a/drivers/video/Kconfig b/drivers/video/Kconfig
> index 5216c11..41fae00 100644
> --- a/drivers/video/Kconfig
> +++ b/drivers/video/Kconfig
> @@ -535,6 +535,15 @@ config FB_VGA16
>  	  To compile this driver as a module, choose M here: the
>  	  module will be called vga16fb.
>  
> +config FB_BF54X_LQ043
> +	tristate "SHARP LQ043 TFT LCD (BF548 EZKIT)"
> +	depends on FB && (BF54x)
> +	select FB_CFB_FILLRECT
> +	select FB_CFB_COPYAREA
> +	select FB_CFB_IMAGEBLIT
> +	help
> +	 This is the framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD
> +
>  config FB_STI
>  	tristate "HP STI frame buffer device support"
>  	depends on FB && PARISC
> diff --git a/drivers/video/Makefile b/drivers/video/Makefile
> index 06eec7b..359e560 100644
> --- a/drivers/video/Makefile
> +++ b/drivers/video/Makefile
> @@ -122,6 +122,7 @@ obj-$(CONFIG_FB_OF)               += offb.o
>  
>  # the test framebuffer is last
>  obj-$(CONFIG_FB_VIRTUAL)          += vfb.o
> +obj-$(CONFIG_FB_BF54X_LQ043)	  += bf54x-lq043.o

It's standard that we suffix all framebuffer drivers with an 'fb'. I'm
making it so in my tree.

Also, you shouldn't place your driver after vfb, that's why there's a
comment that the test framebuffer is last. If someone accidentally
enables vfb, he/she will get a blank screen. So I'm moving it under the
platform driver section. 

Tony




  reply	other threads:[~2007-09-29  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26  3:43 [PATCH 2/2] [VIDEO FRAMEBUFFER] Blackfin BF54x framebuffer device driver for a SHARP LQ043T1DG01 TFT LCD Bryan Wu
2007-09-29  0:09 ` Antonino A. Daplas [this message]
2007-09-29  0:09   ` Antonino A. Daplas

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=1191024570.5273.4.camel@daplas \
    --to=adaplas@gmail.com \
    --cc=bryan.wu@analog.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.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 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.