linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Miguel Ojeda <maxextreme@gmail.com>,
	kernel-discuss@handhelds.org, Luming Yu <Luming.yu@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Andrew Zabolotny <zap@homelink.ru>
Subject: Re: Display class
Date: Wed, 6 Dec 2006 10:57:24 -0800	[thread overview]
Message-ID: <20061206105724.cf7b39bc.randy.dunlap@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612061818540.28745@pentafluge.infradead.org>

On Wed, 6 Dec 2006 18:24:08 +0000 (GMT) James Simmons wrote:

> 
> > > That patch was rought draft for feedback. I applied your comments. This 
> > > patch actually works. It includes my backlight fix as well.
> > 
> > Glad to hear it.  I had to make the following changes
> > in order for it to build.
> > However, I still have build errors for aty.
> 
> Ug. I see another problem. I had backlight completly compiled as a 
> module! Thus it hid these compile errors. So we need also a 
> CONFIG_BACKLIGHT_CLASS_DEVICE_MODULE check as well. Can sysfs handle this 
> well or would it be better the the backlight class be a boolean instead?

SCSI works as a module and it uses sysfs.
See drivers/scsi/scsi_sysfs.c.
Does that answer your question?  I wasn't quite sure what
the question was.

Next question, based on:
drivers/built-in.o: In function `probe_edid':
(.text.probe_edid+0x42): undefined reference to `fb_edid_to_monspecs'

Should backlight and/or display support depend on
CONFIG_FB?  Right now they don't, so the above can happen...

---
~Randy

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-12-06 18:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 19:41 ACPI output/lcd/auxdisplay mess James Simmons
2006-11-14 22:26 ` Miguel Ojeda
2006-11-15  0:54   ` James Simmons
2006-11-16  8:45     ` Miguel Ojeda
2006-11-16 15:38       ` James Simmons
2006-11-16 21:48         ` Miguel Ojeda
2006-12-05 18:03     ` Display class James Simmons
2006-12-06  1:14       ` Randy Dunlap
2006-12-06 15:10         ` James Simmons
2006-12-06 18:14           ` Randy Dunlap
2006-12-06 18:24             ` James Simmons
2006-12-06 18:57               ` Randy Dunlap [this message]
2006-12-06 19:13                 ` James Simmons
     [not found]           ` <Pine.LNX.4.64.0612061443180.28745-nGpKsS7K33UUkNsaar8edxWb9i9o6OzJ@public.gmane.org>
2006-12-06 20:28             ` Randy Dunlap
2006-12-06 13:19       ` Miguel Ojeda
2006-12-30  3:32       ` Dmitry Torokhov
2007-01-13 22:40         ` James Simmons
2007-01-13 22:47           ` [Linux-fbdev-devel] " James Simmons
2007-01-14  7:54           ` Greg KH
2007-01-14  7:55           ` Greg KH

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=20061206105724.cf7b39bc.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=Luming.yu@intel.com \
    --cc=jsimmons@infradead.org \
    --cc=kernel-discuss@handhelds.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxextreme@gmail.com \
    --cc=zap@homelink.ru \
    /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).