linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Richard Purdie" <rpurdie@rpsys.net>
To: linux-fbdev-devel@lists.sourceforge.net, adaplas@hotpop.com
Cc: kronos@people.it
Subject: Re: [patch][revision #2] Add w100 framebuffer driver
Date: Thu, 13 Jan 2005 00:47:28 -0000	[thread overview]
Message-ID: <03ba01c4f909$781fd330$0f01a8c0@max> (raw)
In-Reply-To: 200501130822.26095.adaplas@hotpop.com

Antonino A. Daplas:
> On Sunday 09 January 2005 02:37, Richard Purdie wrote:
>> +static void w100fb_clear_screen(uint32_t mode, long int offset);
>
> I'll submit the patch but would it be better to use u32/u32* and family?

I seem to recall reading somewhere that uint32_t was the preferred form in 
the kernel. The code I was working from used a mixture so I made it 
consistent. If u32 is preferred, I'm happy enough to change it...

> BTW, I'm also submitting Andrew's backlight/lcd patch to akpm. Do you 
> think
> you can port your backlight driver to this framework?

I've been communicating with Andrew offlist and my backlight driver actually 
uses his framework already! It was me who put him onto the blanking event 
idea as that was the previous stumbling block for his patch. I was planning 
on submitting the corgi backlight driver as soon as the class is approved 
(the other code it depends upon has just been approved).

Richard 



-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

  reply	other threads:[~2005-01-13  0:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 18:37 [patch][revision #2] Add w100 framebuffer driver Richard Purdie
2005-01-13  0:22 ` Antonino A. Daplas
2005-01-13  0:47   ` Richard Purdie [this message]
2005-01-13 11:39     ` 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='03ba01c4f909$781fd330$0f01a8c0@max' \
    --to=rpurdie@rpsys.net \
    --cc=adaplas@hotpop.com \
    --cc=kronos@people.it \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).