[Smartphones-kernel] ACPI, Was: Finally, linux-2.6-openmoko into the pkg-fso repository
luca at pca.it
Thu Oct 23 13:56:28 CEST 2008
On Thu, 23 Oct 2008 12:19:16 +0200, Joachim Breitner wrote:
> Am Donnerstag, den 23.10.2008, 10:48 +0200 schrieb Luca Capello:
>> FWIW, however, as soon as I'll compile all the drivers as modules, this
>> will add support for ACPI, which I prefer by far.
> Is ACPI even available on the arm architecture?
I don't know and I've never thought about it. It seems that it's not
available in the upstream FSO kernel.
FWIW, Debian provides four Debian kernels for armel , precisely for
iop32x, ixp4xx, orion5x and versatile: none of them has any CONFIG_ACPI
option, which I guess means that ACPI is not available for ARM :-(
> And if so, is there a good reason why upstream did not include ACPI?
I clearly remember having read something about APM/ACPI in a post from
an Openmoko guy, but I cannot find it right now.
> I’m wondering if it’s a good idea to diverge with the Debian built
> kernel from the FSO kernel – might make debugging harder, and things
> that work on FSO might not in Debian (and vica versa).
While this is true, however my idea is to have the Debian-compiled
kernel as similar as possible to a stock Debian one , which means
that we are obliged to diverge from FSO.
> Maybe at least always have a kernel package ready that is based on the
> FSO code and config?
This is feasible, we just need to choose the package names: something
like linux-image-2.6-openmoko-gta02 and linux-image-2.6-debian-gta02?
However, always to respect the Debian nomenclature , we can either
use linux-image-2.6-openmoko  or linux-image-2.6-samsung or
linux-image-2.6-s3c (my preferred). Then, we could go for
linux-image-2.6-s3c-gta02-fso and linux-image-2.6-s3c-gta02-debian.
Gismo / Luca
 which can change in the future depending on the SoC
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 314 bytes
Desc: not available
More information about the Smartphones-kernel