From owner-freebsd-hackers Fri Nov 8 2: 7:43 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8ACF937B401 for ; Fri, 8 Nov 2002 02:07:42 -0800 (PST) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 326D643E6E for ; Fri, 8 Nov 2002 02:07:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (localhost [127.0.0.1]) by apollo.backplane.com (8.12.5/8.12.5) with ESMTP id gA8A7fFC000752 for ; Fri, 8 Nov 2002 02:07:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.12.5/8.12.5/Submit) id gA8A7fwx000751; Fri, 8 Nov 2002 02:07:41 -0800 (PST) (envelope-from dillon) Date: Fri, 8 Nov 2002 02:07:41 -0800 (PST) From: Matthew Dillon Message-Id: <200211081007.gA8A7fwx000751@apollo.backplane.com> To: hackers@freebsd.org Subject: Int 0x15 and VM86 question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I've been pulling my hair out all night trying to figure out how the hell the VM86 code is able to issue an int 0x15 to the BIOS. I can't find where it gets the interrupt descriptor table entry for int 0x15. My assumption is that it copies it from the idt supplied by the BIOS but I don't see where. As far as I can tell FreeBSD loads a pristine IDT that does not have a record for int 0x15. So how can the VM86 code issue an int 0x15 and have it find the BIOS? If anyone knows the answer to this, I'm all ears! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message