> > Richard, is this actually a bug, or is it a config error or something like > > that? > > > > And should we track it as a post-2.6.20 regression? > > Its a regression IMO. Arguably its a Kconfig error but a nasty one as > the defaults cause the problems. Different people seem to have different > interpretations but to me it appears that the patch from James causes > backlights to fail to turn on for a variety of devices which worked > before.
It is NOT a Kconfig error. The problem is that for many fbdev drivers the backlight code is broken. For some magic reason it only works on pmacs. Most likely because the firmware properly sets up the backlight. Plus we have the conflict with acpi backlight. Think about it. Enabling the backlight code breaks the backlight. Without the backlight driver the default behaviour of the backlight works. Who sets up the default behavior? I don't have a LCD panel with a backlight othewise I would track the problem down. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
