From owner-freebsd-ia64 Sun Sep 9 0: 4:26 2001 Delivered-To: freebsd-ia64@freebsd.org Received: from kayak.xcllnt.net (209-128-86-226.bayarea.net [209.128.86.226]) by hub.freebsd.org (Postfix) with ESMTP id DBA0A37B408 for ; Sun, 9 Sep 2001 00:04:19 -0700 (PDT) Received: from dhcp01.pn.xcllnt.net (dhcp01.pn.xcllnt.net [192.168.4.201]) by kayak.xcllnt.net (8.11.4/8.11.4) with ESMTP id f8974Jf43806 for ; Sun, 9 Sep 2001 00:04:19 -0700 (PDT) (envelope-from marcel@kayak.pn.xcllnt.net) Received: (from marcel@localhost) by dhcp01.pn.xcllnt.net (8.11.6/8.11.3) id f8974Su33402 for ia64@freebsd.org; Sun, 9 Sep 2001 00:04:28 -0700 (PDT) (envelope-from marcel) Date: Sun, 9 Sep 2001 00:04:28 -0700 From: Marcel Moolenaar To: ia64@freebsd.org Subject: Ski port Message-ID: <20010909000427.A33296@dhcp01.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.21i Sender: owner-freebsd-ia64@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Guys, I started working on the ski port today. I have it compiling, but not linking. I have to implement the FreeBDS syscalls first. A thought struck me: what if I, instead of implementing most syscalls so that ski can be used for user processes, I implement an EFI interface first? We're currently not really interested in userland code, so we're going to run ski in "raw" mode anyway. I should be able to hack something together that allows us to work on a real EFI bootloader. With a combination of fake and real ACPI entries we should be able to boot a kernel as if it was running on real hardware, right? Thoughts? -- Marcel Moolenaar USPA: A-39004 marcel@xcllnt.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message