All of lore.kernel.org
 help / color / mirror / Atom feed
From: tgingold@free.fr
To: Robert Millan <rmh@aybabtu.com>
Cc: tgingold@free.fr, The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: IA64 port
Date: Tue, 29 Jan 2008 13:56:49 +0100	[thread overview]
Message-ID: <1201611409.479f22918bed6@imp.free.fr> (raw)
In-Reply-To: <20080129113219.GA22894@thorin>

Quoting Robert Millan <rmh@aybabtu.com>:

> On Tue, Jan 29, 2008 at 11:35:26AM +0100, tgingold@free.fr wrote:
> > Quoting Robert Millan <rmh@aybabtu.com>:
> > > > > Why is this needed?  I'm not sure if it's good to exploit this
> > > "unreliability"
> > > > > feature that fat provides us ;-)
> > > >
> > > > On EFI, the prefix is extracted from an EFI path, whose case may not
> match
> > > > the FAT entries.
> > >
> > > Can you be more specific about this?  What do the specs say?  We wrote
> > > /boot/grub ourselves via grub-install;  is an EFI-compliant firmware
> > > allowed to actively mess up case in paths we provided?
> >
> > On EFI, we don't really know where grub is stored.  There is a filesystem
> > layout convention we'd better to follow.  As a consequence, we extract the
> > path from an EFI structure (I didn't write this code - it's in the EFI
> common
> > code).
>
> What would you think of case-insensitive search in grub_efi_set_prefix() ?

You mean walking the filesystem in grub_efi_set_prefix ?  Humm, this looks
like a hack.  The filesystem may not be FAT and there may be no way to read
directory entries (eg tftp - even if not yet supported).

If you really don't like it I can put it away for now.  Grub should work
without this patch in most cases.

Tristan.



  reply	other threads:[~2008-01-29 12:57 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-28 16:09 IA64 port Tristan Gingold
2008-01-28 16:55 ` Robert Millan
2008-01-29  5:12   ` Tristan Gingold
2008-01-29  9:17     ` Robert Millan
2008-01-29 10:31       ` tgingold
2008-01-29 11:08         ` Robert Millan
2008-01-29  9:59     ` Robert Millan
2008-01-29 10:35       ` tgingold
2008-01-29 11:32         ` Robert Millan
2008-01-29 12:56           ` tgingold [this message]
2008-01-29 13:19             ` Robert Millan
2008-01-29 14:46               ` Marco Gerards
2008-01-29 15:30                 ` Robert Millan
2008-01-29 16:38                   ` tgingold
2008-01-29 18:48                     ` Robert Millan
2008-01-30  5:23                       ` Tristan Gingold
2008-01-30 13:19                         ` Robert Millan
2008-01-29 16:35                 ` tgingold
2008-01-30  5:48                 ` Tristan Gingold
2008-01-30 15:07                   ` Robert Millan
2008-01-30 15:33                     ` Robert Millan
2008-01-30 16:22                     ` tgingold
2008-01-30 18:38                       ` Robert Millan
2008-02-04 15:45                   ` Marco Gerards
2008-02-04 16:07                     ` Robert Millan
2008-02-05  9:51                       ` tgingold
2008-02-10 22:43                   ` Alexandre Boeglin
2008-02-11  8:59                     ` tgingold
2010-01-18 18:03                   ` Robert Millan
2008-01-30  5:48                 ` Tristan Gingold
2008-01-30  5:57                 ` Tristan Gingold
2008-01-30 13:25                   ` Robert Millan
2008-01-30 16:04                     ` tgingold
2008-03-19 17:11                       ` Robert Millan
2008-03-20  6:34                         ` Tristan Gingold
2008-02-05 22:49       ` Alexandre Boeglin
2008-01-29  5:49   ` Tristan Gingold
2008-01-29  9:08     ` Robert Millan
2008-01-29 10:10       ` tgingold
2008-01-29 11:07         ` Robert Millan
2008-01-29 12:53           ` tgingold
2008-01-29 13:39             ` Robert Millan
2008-01-29 13:36     ` Robert Millan

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=1201611409.479f22918bed6@imp.free.fr \
    --to=tgingold@free.fr \
    --cc=grub-devel@gnu.org \
    --cc=rmh@aybabtu.com \
    /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.