From: muta...@gmail.com   
      
   On Thursday, March 23, 2023 at 4:39:07 PM UTC+8, wolfgang kern wrote:   
      
   > > The C library that I use that wraps the UEFI calls is 46k in total    
   > > (executable).    
   >    
   > > I suspect the requirements for UEFI are a modern machine    
   > > with much more than 46k of RAM.   
      
   > it's unfortunately the other way around:    
   > I can't buy any new PC-hardware w/o UEFI on it.   
      
   I don't understand.   
      
   What's wrong with UEFI?   
      
   What's wrong with 46k as part of a BOOTX64.EFI?   
      
   > > You could use the generated assembler, and you could trim    
   > > it down, but is there a purpose to that?   
      
   > there's is no way to trim C-created code. Concept of C is wrong.   
      
   What I meant is that the 46k above can be trimmed   
   down. You don't need the entire C library linked in,   
   depending on what you want to do.   
      
   > > You mentioned you want to see "attempts" (multiple, and    
   > > presumably in assembler) - why? Are you going to use them,    
   > > or you just want to look at them, even if they all have the    
   > > same design?   
      
   > I'm interested how and where to start such an attempt,   
      
   You want to know how to write a hello world using UEFI?   
      
   There are examples on the net, and I have one too   
   (also on the net - but you have to go back to an older   
   version - also on the net - of the code to see that,   
   because I have since moved on from "hello world".   
      
   But the "hello world" code is still there, just commented out:   
      
   https://sourceforge.net/p/pdos/gitcode/ci/master/tree/pdpclib/efistart.c   
      
    if ((Status = print_string ("Hello, world!\n")))    
      
   static EFI_STATUS print_string (char *str) {   
      
   BFN. Paul.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)