All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Zielcke <fzielcke@z-51.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub_halt()
Date: Fri, 27 Nov 2009 22:28:50 +0100	[thread overview]
Message-ID: <1259357330.2789.6.camel@fz.local> (raw)
In-Reply-To: <4B104397.4060806@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]

Am Freitag, den 27.11.2009, 22:24 +0100 schrieb Vladimir
'φ-coder/phcoder' Serbinenko:
> Felix Zielcke wrote:
> > grub_halt is on i386-pc defined as `void grub_halt (int no_apm)' but
> > everywhere else as `grub_halt (void)'
> > util/grub-emu.c has a #ifdef for these 2
> >
> > Shouldn't we just add an int parameter everywhere to make this more
> > simple?
> >
> >   
> I think in future we'll have more different halt methods on different
> platforms. So we could do:
> grub_halt (int methods)
> And have e.g.
> GRUB_HALT_DEFAULT_METHODS
> And e.g. on i386:
> #define GRUB_HALT_DEFAULT_METHODS
> (GRUB_HALT_APM|GRUB_HALT_ACPI|GRUB_HALT_HANG)

Wouldn't be an enum then be better?
But I don't know how to handle this with asm where currently grub_halt()
on i386 seems to be actually defined.

> > grub-emu fails to build on powerpc now because grub/cpu/halt.h
> doestn't
> > exist there:
> >
> https://buildd.debian.org/fetch.cgi?pkg=grub2;ver=1.97%2B20091125-1;ar
> ch=powerpc;stamp=1259179180
> >   

It fails also on sparc because of this.
-- 
Felix Zielcke
Proud Debian Maintainer and GNU GRUB developer

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2009-11-27 21:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-25 20:37 grub_halt() Felix Zielcke
2009-11-27 21:24 ` grub_halt() Vladimir 'φ-coder/phcoder' Serbinenko
2009-11-27 21:28   ` Felix Zielcke [this message]
2009-11-28 19:01   ` grub_halt() Robert Millan
2009-12-04 21:02     ` grub_halt() Robert Millan

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=1259357330.2789.6.camel@fz.local \
    --to=fzielcke@z-51.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.