From: Lubomir Kundrak <lkundrak@redhat.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Make gdb debugging a bit less painful
Date: Fri, 18 Apr 2008 15:58:55 +0200 [thread overview]
Message-ID: <1208527135.16288.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20080418113259.GD26239@thorin>
On Fri, 2008-04-18 at 13:32 +0200, Robert Millan wrote:
> On Thu, Apr 17, 2008 at 10:21:14PM -0400, Pavel Roskin wrote:
> > Quoting Robert Millan <rmh@aybabtu.com>:
> >
> > >Now that I think of it, is there any reason for doing all the cmain()
> > >cruft before grub_main() ? Getting to grub_main() only requires a working
> > >stack, which we have, and grub_main() inmediately returns control back to
> > >architecture-specific code in grub_machine_init().
> > >
> > >So why not move from:
> > >
> > > _start -> cmain -> grub_main
> > >
> > >to:
> > >
> > > _start -> grub_main -> grub_machine_init -> cmain
> > >
> > >?
> >
> > I think it would be great. We should try to make the code for
> > different architectures more uniform to simplify maintenance.
>
> Here. Unfortunately I can't test it as I have no ieee1275 at hand currently.
>
> Anyone?
I have an OLPC XO machine borrowed now. I will test that this evening.
--
Lubomir Kundrak (Red Hat Security Response Team)
next prev parent reply other threads:[~2008-04-18 13:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 22:30 [PATCH] Make gdb debugging a bit less painful Lubomir Kundrak
2008-04-15 13:21 ` Robert Millan
2008-04-15 13:38 ` Robert Millan
2008-04-17 11:53 ` Lubomir Kundrak
2008-04-17 20:11 ` Robert Millan
2008-04-18 2:21 ` Pavel Roskin
2008-04-18 11:32 ` Robert Millan
2008-04-18 12:13 ` Robert Millan
2008-04-18 15:16 ` Pavel Roskin
2008-04-18 15:36 ` Robert Millan
2008-04-18 15:38 ` Bean
2008-04-18 15:45 ` Robert Millan
2008-04-18 13:58 ` Lubomir Kundrak [this message]
2008-04-18 15:54 ` Robert Millan
2008-04-15 19:01 ` Pavel Roskin
2008-04-17 11:54 ` Lubomir Kundrak
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=1208527135.16288.2.camel@localhost.localdomain \
--to=lkundrak@redhat.com \
--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.