[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20061206105724.cf7b39bc.randy.dunlap@oracle.com>
Date: Wed, 6 Dec 2006 10:57:24 -0800
From: Randy Dunlap <randy.dunlap@...cle.com>
To: James Simmons <jsimmons@...radead.org>
Cc: Miguel Ojeda <maxextreme@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Fbdev development list
<linux-fbdev-devel@...ts.sourceforge.net>,
Luming Yu <Luming.yu@...el.com>,
Andrew Zabolotny <zap@...elink.ru>, linux-acpi@...r.kernel.org,
kernel-discuss@...dhelds.org
Subject: Re: Display class
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists