From: James Bottomley <James.Bottomley@steeleye.com>
To: Andrey Panin <pazke@orbita1.ru>
Cc: Dave Jones <davej@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series)
Date: Fri, 14 Jun 2002 10:14:38 -0400 [thread overview]
Message-ID: <200206141414.g5EEEci22528@localhost.localdomain> (raw)
In-Reply-To: Message from Andrey Panin <pazke@orbita1.ru> of "Fri, 14 Jun 2002 17:52:29 +0400." <20020614135229.GA313@pazke.ipt>
pazke@orbita1.ru said:
> IMHO Voyagers are too old and big machines to get (working) APM, and
> visws have no BIOS or limited BIOS emulation.
That depends what you mean by `apm'. In kernel/apm.c, it's tied to the
existence of the APM bios and since voyagers have no bios per say (they
actually have a SUS, which is an actively running boot OS on a tiny i386
processor which can emulate a minimal PC bios when in PC mode) then you're
correct.
Running Linux on a voyager, I can power off the machine, read the internal
power source, the status of the front panel switch and even trigger a power
management shutdown after the AC power is lost for a certain length of time
(voyagers usually have internal lead acid batteries). The way it's currently
set up, if I turn off the front panel switch, the machine will execute a clean
shutdown and power itself off when the shutdown is finished. (this is mainly
done in the voyager_thread.c file, where it keeps a kernel daemon permanently
monitoring the machine status, if you're interested).
The above are all traditional APM functions, I just don't need apm.c to do
them.
However, apm.c is still in arch/i386/kernel, just in case, so I think
mpparse.c should join it, and we should keep all the other pieces (bootflag.c
and acpi.c) in there just in case.
James
next prev parent reply other threads:[~2002-06-14 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:54 James Bottomley
2002-06-13 8:20 ` Andrey Panin
2002-06-13 15:48 ` James Bottomley
2002-06-13 23:17 ` Dave Jones
2002-06-14 0:13 ` James Bottomley
2002-06-14 0:45 ` Dave Jones
2002-06-14 2:19 ` Matthew D. Pitts
2002-06-14 2:52 ` SCSI host/channel/lun/part to /dev/sd* or maj/minor mapping Mark Atwood
2002-06-14 13:41 ` [PATCH: NEW SUBARCHITECTURE FOR 2.5.21] support for NCR voyager (3/4/5xxx series) Andrey Panin
2002-06-14 13:49 ` Dave Jones
2002-06-14 13:52 ` Andrey Panin
2002-06-14 14:14 ` James Bottomley [this message]
2002-06-14 14:16 ` Dave Jones
2002-06-17 13:36 ` Andrey Panin
2002-06-17 14:03 ` Dave Jones
2002-06-16 0:00 ` James Bottomley
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=200206141414.g5EEEci22528@localhost.localdomain \
--to=james.bottomley@steeleye.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pazke@orbita1.ru \
/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
all inboxes | Powered by JetHome®