All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: suspend command patch
Date: Mon, 03 Jan 2005 21:42:42 +0000	[thread overview]
Message-ID: <87hdly2nql.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20050103182344.GA30549@miracle> (Hollis Blanchard's message of "Mon, 3 Jan 2005 12:23:44 -0600")

Hollis Blanchard <hollis@penguinppc.org> writes:

> Now that module support is within reach, this patch implements the Open
> Firmware "enter" command, which allows us to get back to the interactive
> OF prompt after loading a client program (GRUB).

Nice!

> As discussed previously, the GRUB command name is "suspend", and the
> file is in a new commands/ieee1275 directory, as it should work on all
> Open Firmware architectures.

Before this can be checked in, I want to wait until Okuji agrees with
this directory layout.

> I have successfully tested this on my G3. The briQ seems to have an
> unfortunate bug: "enter" works, but running "go" to resume GRUB results
> in GRUB being re-entered from its entry point. I wonder if this bug
> still affects later Codegen releases (i.e the Pegasos)...
>
I can test this and I will let you know.

> +static grub_err_t
> +grub_cmd_suspend (struct grub_arg_list *state, int argc, char **args)
> +{
> +  (void)state;
> +  (void)argc;
> +  (void)args;

Better use an attribute for this.

> +  grub_printf("Run 'go' to resume GRUB.\n");
> +  grub_ieee1275_enter();

Can you add a space before the ()?

Thanks,
Marco




  reply	other threads:[~2005-01-03 21:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-03 18:23 suspend command patch Hollis Blanchard
2005-01-03 21:42 ` Marco Gerards [this message]
2005-01-18  5:19   ` Hollis Blanchard
2005-01-18 10:52     ` Yoshinori K. Okuji

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=87hdly2nql.fsf@marco.marco-g.com \
    --to=metgerards@student.han.nl \
    --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.