Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH 1/2]Freescale i.MX framebuffer driver
Date: Fri, 18 Mar 2005 03:44:58 +0800	[thread overview]
Message-ID: <200503180344.58891.adaplas@hotpop.com> (raw)
In-Reply-To: <20050317173624.GA29286@metis.extern.pengutronix.de>

On Friday 18 March 2005 01:36, Sascha Hauer wrote:
> Hello all,
>
> This Patch adds support for the framebuffer on the freescale i.MX SOC
> architecture. The driver has been tested on the mx1ads board, the pimx1
> board and another custom board with different displays.

Preliminary comments:

1. Can you use framebuffer_alloc()?  Meaning you have to change this:

struct imxfb_info {
       struct fb_info          fb;
	...
}

Then put all driver private data in info->par.

2. Comment on putting the blank function in the workqueue:  The console
expects that after calling fbcon_blank/fb_blank, that the hardware is really
in that state.  For example, after calling unblank(), the console expects
that it is entirely safe to write to the device because it will do so.

If it is indeed safe to access the  device on all blank states, then yes, a
workqueue should be fine.

3. Also add a Signed-off-by line and submit the patch inline.

Tony





-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-03-17 19:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 17:36 [PATCH 1/2]Freescale i.MX framebuffer driver Sascha Hauer
2005-03-17 19:44 ` Antonino A. Daplas [this message]
2005-03-18 11:39   ` Sascha Hauer
2005-03-18 14:14     ` Antonino A. Daplas
2005-03-18 17:54       ` Sascha Hauer
2005-03-18 18:48         ` Geert Uytterhoeven
2005-03-18 20:47         ` Antonino A. Daplas
2005-03-22  9:31           ` Sascha Hauer

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=200503180344.58891.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=s.hauer@pengutronix.de \
    /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