Date: Sun, 9 Sep 2001 17:28:59 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Peter Wemm <peter@wemm.org> Cc: John Baldwin <jhb@FreeBSD.org>, <cvs-committers@FreeBSD.org>, <cvs-all@FreeBSD.org>, Doug Rabson <dfr@FreeBSD.org> Subject: Re: cvs commit: src/sys/boot/efi/libefi efifs.c Makefile efiboot Message-ID: <20010909172602.J406-100000@salmon.nlsystems.com> In-Reply-To: <20010908211814.0C6F6380A@overcee.netplex.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 8 Sep 2001, Peter Wemm wrote: > John Baldwin wrote: > > > > On 07-Sep-01 Doug Rabson wrote: > > > On Fri, 7 Sep 2001, John Baldwin wrote: > > > > > >> > > >> On 07-Sep-01 Doug Rabson wrote: > > >> > dfr 2001/09/07 01:51:48 PDT > > >> > > > >> > Modified files: > > >> > sys/boot/efi/libefi Makefile efiboot.h > > >> > Added files: > > >> > sys/boot/efi/libefi efifs.c > > >> > Log: > > >> > Add a libstand filesystem for accessing EFI native filesystems. > > >> > > >> Woot! So how far along are you know? Can you read a kernel into memory > > >> now? > > > > > > Of course not :-). I can open the file and read some bytes from it. > > > > Hmmm, ok. So what's stopping you from opening the file named "kernel" and > > sticking its bytes in one contiguous slab in memory? :) Granted, the current > > kernel doesn't have any sort of non-ski console driver AFAIK. > > I built a libstand and loader.efi, after upgrading the SDV box to the current > B17A firmware and loader.efi basically does this: > > fs0:\> loader > > Console: EFI Console > > FreeBSD/ia64 EFI boot, Revision 0.1 > (peter@mhostname time date of build) > not found > <hang> > > The before the EFI upgrade, it didn't print the " not found" message before > the hang. > > This was at about 5am and I was out of time, so I didn't get much chance > to tinker. As a bonus, the B117A upgrade killed the linux installation > on the disk.. It now fails when lilo / eli start up with "_PRT not found" > so something pretty close to that. Hmm. I'm not sure what is wrong here - my firmware is a couple of months old so perhaps that makes a difference. At least you have printf working anyway. I suggest spraying calls to printf all over the place until you find roughly where it hangs. One possible problem is that the procedure for building the EFI executable is pretty fragile. If the ELF file contains any sections which are not listed in the objcopy line in the Makefile then it will not work properly. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010909172602.J406-100000>