linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: adaplas@gmail.com
Cc: akpm@osdl.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 01/10] fbdev: Clean up of sparc FB options
Date: Wed, 16 May 2007 14:47:39 -0700 (PDT)	[thread overview]
Message-ID: <20070516.144739.41633447.davem@davemloft.net> (raw)
In-Reply-To: <464B74EE.5040407@gmail.com>

From: "Antonino A. Daplas" <adaplas@gmail.com>
Date: Thu, 17 May 2007 05:17:34 +0800

> From: Krzysztof Helt <krzysztof.h1@wp.pl>
> 
> This patch puts all SBUS/UPA selection under one option "SBUS/UPA
> framebuffers" and moves all sparc specific drivers next to them
> in one group.
> 
> Signed-off-by: Krzysztof Helt <krzysztof.h1@wp.pl>
> Signed-off-by: Antonino Daplas <adaplas@gmail.com>

Thanks for cleaning this up.

Signed-off-by: David S. Miller <davem@davemloft.net>

On a related note I've been trying to figure out how to solve a
particular issue on sparc, perhaps you can help?

The firmware has properties that we could use to determine exactly
which framebuffer device is being used as the console in multi-head
situations.

Currently there is no easy way to make use of that so the user just
gets whatever the framebuffer device probing order gives them which
isn't nice and is often wrong.

One idea I have is to provide a way to set some flag in the
fbinfo.  The flag would indicate that this framebuffer should
be used as the primary console by default.  Command line options
et al. could of course override this.

In this way sparc framebuffers could see if a device is the
one the "output-device" firmware property points to, and if
so it would set the flag.

What do you think about this?

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/

  reply	other threads:[~2007-05-16 21:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16 21:17 [PATCH 01/10] fbdev: Clean up of sparc FB options Antonino A. Daplas
2007-05-16 21:47 ` David Miller [this message]
2007-05-16 23:15   ` Antonino A. Daplas
2007-05-16 23:17     ` David Miller
2007-05-17  0:01       ` Antonino A. Daplas
2007-05-17  0:05         ` David Miller
2007-05-17  0:10           ` Antonino A. Daplas
2007-05-17  0:15             ` David Miller
2007-05-17  0:36               ` Antonino A. Daplas
2007-05-17  0:42                 ` David Miller

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=20070516.144739.41633447.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=adaplas@gmail.com \
    --cc=akpm@osdl.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 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).