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: normal mode chainloader
Date: Thu, 01 Jul 2004 15:30:26 +0200	[thread overview]
Message-ID: <87hdsram8d.fsf@marco.marco-g.com> (raw)
In-Reply-To: <20040701115321.GA21964@artax.karlin.mff.cuni.cz> (Tomas Ebenlendr's message of "Thu, 1 Jul 2004 13:53:21 +0200")

ebik@artax.karlin.mff.cuni.cz (Tomas Ebenlendr) writes:

> ad copyright:
> I will send the copyright snail-mail at this friday. Then I'm leaving to
> Norway for one month.

I think Okuji will get a message from the FSF about this.  I think it
is safe to assume the FSF will receive the mail and to apply the
patch. :)

Or Okuji, do you really want to wait for the FSF to confirm this
assignment?

> ad modules:
> In fact the dependencies are written somewhere in elf format and
> depmod.lst is only for user to see what depends on what.

So that doesn't mean _chain gets autoloaded?

> autoloading:
> I wrote simple cmd-autoloading patch, but it triggers some mm-bug which I hunt
> now. Moreover my network card in my laptop (where I hack for grub) is broken,
> so I will post the patch when I return.

Which bugs are those?  I had some mm problems with the PPC port as
well.

If it is incorrect usage of malloc and free, you could use valgrind.

> ad normal mode chainloader:
> Consider moving loader/i386/pc/chainloader_normal.c to
> commands/chainloader.c. I don't know which placement is better. (This
> file will not contain any architecture dependent code as long as
> arguments passed to command chainloader will be same for all
> architectures.)

No, the chainloader is for the PC only.  And it depends on something
that is arch specific.

Thanks,
Marco




  reply	other threads:[~2004-07-01 13:32 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21 18:00 normal mode chainloader Tomas Ebenlendr
2004-06-22  9:00 ` Marco Gerards
2004-06-22 11:33   ` Tomas Ebenlendr
2004-06-22 19:52     ` Marco Gerards
2004-06-23  7:10       ` Tomas Ebenlendr
2004-06-23 10:34         ` Yoshinori K. Okuji
2004-06-23 10:40           ` Tomas Ebenlendr
2004-06-22 11:41   ` Tomas Ebenlendr
2004-06-22 20:25     ` Marco Gerards
2004-06-23  7:29       ` Tomas Ebenlendr
2004-06-23 10:55         ` Marco Gerards
2004-06-23 17:20           ` Jeroen Dekkers
2004-06-23  8:11       ` Copyright crap Was: " Tomas Ebenlendr
2004-06-23  8:59         ` Jeroen Dekkers
2004-06-23 10:43           ` Tomas Ebenlendr
2004-06-23 11:58       ` Tomas Ebenlendr
2004-06-23 16:49         ` Marco Gerards
2004-06-24  8:44           ` Tomas Ebenlendr
2004-06-24 15:26             ` Marco Gerards
2004-06-24 16:51               ` Tomas Ebenlendr
2004-07-01 10:54                 ` Marco Gerards
2004-07-01 11:17                   ` Yoshinori K. Okuji
2004-07-01 11:53                     ` Tomas Ebenlendr
2004-07-01 13:30                       ` Marco Gerards [this message]
2004-07-01 16:03                         ` history, autoloading was: " Tomas Ebenlendr
2004-09-10 22:05                         ` Marco Gerards
2004-09-12 12:46         ` Marco Gerards
2004-09-17 18:48           ` Tomas Ebenlendr
2004-09-17 18:53             ` M. Gerards
2004-09-17 19:32               ` Tomas Ebenlendr
2004-09-17 19:38                 ` M. Gerards
2004-09-20  6:58                   ` Tomas Ebenlendr
2004-09-21  8:22                     ` Module loading - grub-emu, bug in kern/dl.c Tomas Ebenlendr
2004-11-17 15:43                       ` Marco Gerards
2004-11-17 20:30                         ` Tomas Ebenlendr
2004-11-17 20:45                           ` Marco Gerards
2004-11-22 15:18                         ` Timothy Baldwin

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=87hdsram8d.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.