From: Nils Faerber <nils.faerber-t93Ne7XHvje5bSeCtf/tX7NAH6kLmebB@public.gmane.org>
To: "Williams,
Richard"
<Richard.Williams-RyImI6ggfRp0+Iju73vM4UEOCMrvLtNR@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI for x-scale
Date: Mon, 09 May 2005 21:31:31 +0200 [thread overview]
Message-ID: <427FBA93.1060309@kernelconcepts.de> (raw)
In-Reply-To: <6EF58BF68042DF4AA46A54994117D64F035A1C81-x6Fv9fcoW1YgtwCHe4clqUEOCMrvLtNR@public.gmane.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Williams, Richard wrote:
> Hi,
Hi!
> I'm a newbie to the ACPI world.
> Has anyone ported the Linux 2.6 kernel ACPI to the ARM processors -
> specifically an Intel X-scale, PXA-270 ?
ROTFL ;)
Sorry... couldn't resist...
> Is this appropriate for an embedded single board computer ?
No, it isn't.
It starts with the "problem" that the usual ARM/StrongARM/XScale device
do not own a BIOS as it is known on x86 PCs.
For most embedded platforms implementing huge systems like APM or ACPI
is simply a waste of time - you simply do it yourself in the specific
kernel you are using on your platform anyway.
IMHO ACPI and APM are used as a generic approach, i.e. for situation
where you do not know specifics of the system you are running on. Then
ACPI offers for example a method to suspend, resume or power throttle a
device (put to standby, suspend, ...).
The more complex systems became the more complex those sophisticated
system became with ACPI being its current culprit.
The current embedded Linux flavours all do power management to various
degrees by themselves, expecially using the current Linux device model
and power state siganlling, i.e. the device drivers have to do their own
power management.
Or to make it short: No, you do not want to implement ACPI for embedded
platforms.
> Thanks,
> Rich
CU
nils faerber
- --
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
- --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCf7qTJXeIURG1qHgRAlZrAJ0cbKE2ZeckBf2o7qKHQyxAUDsGHwCfcip9
4+HZrQQfFW8BZW2/RjPK/F0=
=v0io
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-05-09 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-09 18:55 ACPI for x-scale Williams, Richard
[not found] ` <6EF58BF68042DF4AA46A54994117D64F035A1C81-x6Fv9fcoW1YgtwCHe4clqUEOCMrvLtNR@public.gmane.org>
2005-05-09 19:31 ` Nils Faerber [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-09 20:10 Williams, Richard
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=427FBA93.1060309@kernelconcepts.de \
--to=nils.faerber-t93ne7xhvje5bsectf/tx7nah6klmebb@public.gmane.org \
--cc=Richard.Williams-RyImI6ggfRp0+Iju73vM4UEOCMrvLtNR@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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