From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: James Simmons <jsimmons@infradead.org>
Cc: arief# <arief_m_utama@telkomsel.co.id>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Radeon Framebuffer Driver in 2.6.3?
Date: Sat, 28 Feb 2004 09:43:27 +1100 [thread overview]
Message-ID: <1077921806.22962.43.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.44.0402271755090.2216-100000@phoenix.infradead.org>
On Sat, 2004-02-28 at 05:00, James Simmons wrote:
> > Can you test the patch below ? :
>
> Just a couple of things. The idea of adding another field to
> con_blank bothers me. I think the better approach is to add more flags.
Linus proposed the additional parameter approach ;
> > - if (memcmp(&info->var, var, sizeof(struct fb_var_screeninfo))) {
> > + if ((var->activate & FB_ACTIVATE_FORCE) ||
> > + memcmp(&info->var, var, sizeof(struct fb_var_screeninfo))) {
> > if (!info->fbops->fb_check_var) {
> > *var = info->var;
> > return 0;
>
> Ug!!! Another flag. How about instead in fbcon.c we call set_par directly
> instead of messing with fb_set_var.
Because fb_set_par is the proper interface, I want to get rid of all
the direct calls to the fbdev made by fbcon in the end. Calling
set_par directly will also skip the notification of the clients,
which may be just what we want for fbcon and harmful the day some
other client relies on that mecanism (and I already have one example
on ppc).
> Let me play with some ideas. I can have a another patch ready over the
> weekend.
Well... I was about to submit this one...
Ben.
next prev parent reply other threads:[~2004-02-27 22:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 6:27 Radeon Framebuffer Driver in 2.6.3? arief#
2004-02-27 7:04 ` Benjamin Herrenschmidt
2004-02-27 10:06 ` arief#
2004-02-27 9:56 ` Benjamin Herrenschmidt
2004-02-27 10:45 ` Zilvinas Valinskas
2004-02-27 17:19 ` Mike Houston
2004-02-27 18:00 ` James Simmons
2004-02-27 22:43 ` Benjamin Herrenschmidt [this message]
2004-02-28 0:58 ` James Simmons
2004-02-28 1:37 ` Benjamin Herrenschmidt
2004-03-02 0:22 ` James Simmons
2004-03-02 0:26 ` Benjamin Herrenschmidt
2004-03-02 3:08 ` Paul Jackson
2004-03-02 7:50 ` Paul Jackson
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=1077921806.22962.43.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=arief_m_utama@telkomsel.co.id \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@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 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.