[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IA64 port
From: |
tgingold |
Subject: |
Re: IA64 port |
Date: |
Tue, 29 Jan 2008 11:35:26 +0100 |
User-agent: |
Internet Messaging Program (IMP) 3.2.8 |
Quoting Robert Millan <address@hidden>:
> > > 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).
Did I answer to all your concerns on this topic ?
- IA64 port, Tristan Gingold, 2008/01/28
- Re: IA64 port, Robert Millan, 2008/01/28
- Re: IA64 port, Robert Millan, 2008/01/29
- Re: IA64 port,
tgingold <=
- Re: IA64 port, Robert Millan, 2008/01/29
- Re: IA64 port, tgingold, 2008/01/29
- Re: IA64 port, Robert Millan, 2008/01/29
- Re: IA64 port, Marco Gerards, 2008/01/29
- Re: IA64 port, Robert Millan, 2008/01/29
- Re: IA64 port, tgingold, 2008/01/29
- Re: IA64 port, Robert Millan, 2008/01/29
- Re: IA64 port, Tristan Gingold, 2008/01/30
- Re: IA64 port, Robert Millan, 2008/01/30
- Re: IA64 port, tgingold, 2008/01/29