From owner-freebsd-current Wed Nov 20 11:39:14 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA29267 for current-outgoing; Wed, 20 Nov 1996 11:39:14 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA29260 for ; Wed, 20 Nov 1996 11:39:12 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id LAA15371 for ; Wed, 20 Nov 1996 11:39:10 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id GAA18450; Thu, 21 Nov 1996 06:30:35 +1100 Date: Thu, 21 Nov 1996 06:30:35 +1100 From: Bruce Evans Message-Id: <199611201930.GAA18450@godzilla.zeta.org.au> To: Christian.Gusenbauer@utimaco.co.at, joerg_wunsch@uriah.heep.sax.de Subject: Re: cdrom boot? Cc: Christian.Gusenbauer@safeconcept.utimaco.co.at, freebsd-current@freebsd.org Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I tried to port fbsdboot to bcc a year ago. Unfortunately, bcc doesn't >understand inline assembler statements (AFAIR) Yes it does: int main(argc, argv) int achar **argv; { int foo; ; /* end declarations to get frame allocated */ #asm ; Offsets are relative to sp so they are only easy to use on x86's ; for x >= 3. mov ax,_main.argc[sp] mov bx,_main.argv[sp] mov cx,_main.foo[sp] mov dx,1 ... #endasm } >and I'm not very familar >with the unix assembler. It doesn't use "the" unix assembler. >Does bcc support 32bit pointers/addresses (like >the 'far' masm statement)? No. It only supports pure tiny and small models. Bruce