All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: mono, gray and index configs
Date: Fri, 19 Aug 2005 23:09:55 -0400	[thread overview]
Message-ID: <9e473391050819200950020d7@mail.gmail.com> (raw)
In-Reply-To: <43069BE0.80604@gmail.com>

The patch is just for testing, don't send it on. The radeonfb portion
is definitely not finished.

This adds an optional function to each driver that advertises what
configs it offers.

+char *radeonfb_getconfigs(struct fb_info *info)
+{
+	return "I4\nI8\nA1R5G5B5\nR5G6B5\nR8G8B8\nA8R8G8B8\nA4R4G4B4\nA8I8\nA2R10G10B10\n";
+}
 
  static struct fb_ops radeonfb_ops = {
 	.owner			= THIS_MODULE,
@@ -1873,6 +1909,7 @@ static struct fb_ops radeonfb_ops = {
 	.fb_fillrect		= radeonfb_fillrect,
 	.fb_copyarea		= radeonfb_copyarea,
 	.fb_imageblit		= radeonfb_imageblit,
+	.fb_get_configs		= radeonfb_getconfigs,
 };

If you know what configs the driver support try setting them via the
sysfs attribute. You can also check out your config match code by
putting in non-supported configs and setting what gets returned in the
attribute.

-- 
Jon Smirl
jonsmirl@gmail.com


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-08-20  3:10 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-11  3:21 mono, gray and index configs Jon Smirl
2005-08-11  5:36 ` Antonino A. Daplas
2005-08-11  8:22   ` Geert Uytterhoeven
2005-08-11 11:08     ` Antonino Daplas
2005-08-11 11:49       ` Geert Uytterhoeven
2005-08-11 17:34         ` Antonino A. Daplas
2005-08-11 19:14           ` Jon Smirl
2005-08-20  1:13             ` Jon Smirl
2005-08-20  2:56               ` Antonino A. Daplas
2005-08-20  3:09                 ` Jon Smirl [this message]
2005-08-22 10:17                   ` Geert Uytterhoeven
2005-08-22 13:30                     ` Richard Smith
2005-08-22 14:06                       ` Geert Uytterhoeven
2005-08-22 14:36                         ` Richard Smith
2005-08-22 15:47                           ` Antonino A. Daplas
2005-08-22 17:19                           ` Geert Uytterhoeven
2005-08-22 19:00                             ` Richard Smith
2005-08-22 19:44                               ` Richard Smith
2005-08-22 15:57                     ` Jon Smirl
2005-08-12  7:24           ` Geert Uytterhoeven
2005-08-12 10:28             ` Antonino A. Daplas
2005-08-11  8:20 ` Geert Uytterhoeven

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=9e473391050819200950020d7@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@gmail.com \
    --cc=geert@linux-m68k.org \
    --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 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.