Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Vesa Jääskeläinen" <chaac@nic.fi>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: RFC: conf/i386.rmk
Date: Tue, 05 Aug 2008 09:58:12 +0300	[thread overview]
Message-ID: <4897FA04.1060001@nic.fi> (raw)
In-Reply-To: <1217825941.10989.26.camel@dv>

Pavel Roskin wrote:
> On Sun, 2008-08-03 at 21:30 +0200, Robert Millan wrote:
>> On Sun, Aug 03, 2008 at 09:28:39PM +0200, Robert Millan wrote:
>>> Hi,
>>>
>>> I'm thinking that we have quite a bit of duplicate stuff in each of the 4
>>> i386 ports (cpuid, pci, serial, etc) that could well live in a
>>> firmware-agnostic conf/i386.rmk file.
>>>
>>> This would simplify things and make them easier to maintain.  What do you
>>> think?
>> Btw, I think grub-emu could go there too.  The only arch-specific thing in
>> it AFAICS is cpuid.mod.
> 
> I tried moving more stuff to common.rmk many times but gave up every
> time.  One of the reasons is that the sparc64 support is very
> out-of-date and doesn't use common.rmk at all.  I cannot even test it
> (well, I haven't tries hard).

If sparc64 support is out of date and the maintainer is nowhere to be 
seen then I think you can put that support to graveyard until someone 
comes up to update it. Putting all common stuff to every platform to 
common.rmk is a good way and the only way (in my opinion) to go forward.



  reply	other threads:[~2008-08-05  7:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 19:28 RFC: conf/i386.rmk Robert Millan
2008-08-03 19:30 ` Robert Millan
2008-08-04  4:59   ` Pavel Roskin
2008-08-05  6:58     ` Vesa Jääskeläinen [this message]
2008-08-05 16:49       ` Pavel Roskin
2008-08-05 20:07         ` Robert Millan
2008-08-05 21:08           ` Pavel Roskin
2008-09-05 10:54             ` [PATCH] Move cpuid.mod to conf/i386.rmk (Re: RFC: conf/i386.rmk) Robert Millan
2008-09-07 17:13               ` Robert Millan
2008-08-04 22:08   ` RFC: conf/i386.rmk Marco Gerards

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=4897FA04.1060001@nic.fi \
    --to=chaac@nic.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox