On Fri, 20 Nov 2009 15:39:41 +0100 Michael 'Mickey' Lauer <[email protected]> wrote:
> Am Freitag, den 20.11.2009, 15:30 +0100 schrieb Marcin Juszkiewicz: > > Dnia piątek, 20 listopada 2009 o 15:24:39 Sebastian Spaeth > > napisał(a): > > > > > Better suggestions on how to achieve this are welcome. > > > > In distro config: > > > > MACHINE_FEATURES_om-gta01 = "this that those butnoapm" > > > > This way your distro has what you want and others have what was set > > in machine config. > > Good idea. > > For the records though, I would consider it being the machine > maintainer's call to define the machine config. If he decides that apm > is very misleading on said machine, perhaps because without taking > special care about the peripheral devices there will no be proper > suspend in the first place, then I might be inclined to follow this > reasoning and leave apm out there... > That indicates to me that FSO is broken. The last I checked any application which has opened /dev/apm_bios can choose to hold off the suspend until it has finished doing stuff(tm) Turning off machine features for a broken DISTRO sounds wrong. Graeme _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
