This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC and 16-bit mode for x86 processor when writing boot code.

From: "Ivan Pulleyn" <ivan dot pulleyn at gmail dot com>
To: "Smith, Stephen (SWCOE)" <Stephen dot Smith at honeywell dot com>
Cc: binutils at sourceware dot org
Date: Mon, 26 Feb 2007 15:15:19 -0800
Subject: Re: GCC and 16-bit mode for x86 processor when writing boot code.
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SBxzHuG3VF8kOBQJ8Jp4yF31qE+Vmwz4WCo447bASSKtSuwSfCGurlhhjqWxAo5TdcNcWdvoZN9uGXLq10w8ZdnBqPu7WnMIDgb0SV81LIAVVI00+YbQnB6tGf57WmW9bMGvvIv7w8Y8MErlibO18mK8h/zMIhjsTY/UzoTRKJ0=
References: <45E31B7E.1070704@avtrex.com> <EF244E26469B2C42B2B72AC465843D6B044FBED8@AZ18EV808.global.ds.honeywell.com>

I have found that recent versions of gas allow use of the .code16
directive in assembler source targeting x86. I was able to write my
bootsector using this method.

Ivan...

On 2/26/07, Smith, Stephen (SWCOE) <Stephen.Smith@honeywell.com> wrote:

I am writing some boot code for an x86 processor.  I know that binutils
assumes 32-bit mode and doesn't have anything analogous to code16.

What is the normal way of handling the 16bit mode until you've run
enough code to switch to 32-bit flat mode?  Any document I can look at?

BTW, I am using binutils 2.17.

References:
- Re: Binutils 2.17 fails `make check` on mipsel-linux-gnu
  - From: David Daney
- GCC and 16-bit mode for x86 processor when writing boot code.
  - From: Smith, Stephen \(SWCOE\)

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]