All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Possible improvements to build system
Date: Sat, 28 Feb 2009 12:50:10 +0100	[thread overview]
Message-ID: <20090228115010.GA22149@thorin> (raw)
In-Reply-To: <49A91C92.2030708@gmail.com>

On Sat, Feb 28, 2009 at 12:14:26PM +0100, phcoder wrote:
> 2. ata.mod, hdparm.mod, ata_pthru.mod, usbms.mod, ohci.mod, uhci.mod,  
> usbtest.mod, usb.mod, memdisk.mod
> I don't see why these modules are in i386-pc.rmk and not in common.rmk

This is because nobody implemented grub_in* and grub_out* functions on
powerpc.  But in the meantime, they could move to i386.rmk.

As for memdisk, it used to depend on the image format (thus PE had to be
excluded), but IIRC this is not so anymore.  It could move to common.rmk.

> 3. kernel.img, grub-setup
> These contain a number of files shared by all platforms. Like e.g.  
> filesystems. I propose to create an additional file common-pre.rmk which  
> could contain the variables like
> FS_files=...
> which platform-specific files can use later

This is trickier than it seems.  Many of the gen* scripts parse those files
and changing them this way would break stuff.  It needs to be done carefully.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."



      reply	other threads:[~2009-02-28 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-28 11:14 Possible improvements to build system phcoder
2009-02-28 11:50 ` Robert Millan [this message]

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=20090228115010.GA22149@thorin \
    --to=rmh@aybabtu.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.