All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: grub-devel@gnu.org
Subject: firmware specification
Date: Sun, 7 May 2006 19:58:30 +0200	[thread overview]
Message-ID: <200605071958.31434.okuji@enbug.org> (raw)

So far, we've been using the triples (such as i386-pc-gnu) to specify both a 
CPU and a firmware. I feel that this is not appropriate. The vendor part of 
the triple can imply what firmware is used, but not always. So, for example, 
I invented i386-efi for EFI. Since the specification of the triple affects 
the choice of a compiler, I suspect that our usage is wrong.

So I'd like to add a configuration option to specify a firmware type instead 
of using a vendor name. When the user does not specify her firmware 
explicitly, configure can guess the firmware from the CPU and the vendor.

Is there any objection?

Okuji



                 reply	other threads:[~2006-05-07 17:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200605071958.31434.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.