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 16:17:17 -0700 (PDT)	[thread overview]
Message-ID: <20070516.161717.115911096.davem@davemloft.net> (raw)
In-Reply-To: <1179357305.4743.20.camel@daplas>

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

> A flag may be the easiest. But we can also define an arch-specific
> function (ie, fb_get_primary_device()) in asm/fb.h. With the x86, this
> can be easily done by checking the IORESOURCE_ROM_SHADOW bit flag.  
> 
> I'll add this for the x86, and then perhaps others can follow suit.

What would this iterate over?  The list of all registered
fb_info's?

Anyways this sounds great, I'll add the sparc bits once you
push the x86 version.

-------------------------------------------------------------------------
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 23:17 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
2007-05-16 23:15   ` Antonino A. Daplas
2007-05-16 23:17     ` David Miller [this message]
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.161717.115911096.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).