All of lore.kernel.org
 help / color / mirror / Atom feed
From: DervishD <raul@pleyades.net>
To: immortal1015 <immortal1015@52mail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: A newbie's question
Date: Thu, 26 Sep 2002 18:14:24 +0200	[thread overview]
Message-ID: <20020926161424.GF47@DervishD> (raw)
In-Reply-To: <20020926144558Z261317-8740+1711@vger.kernel.org>

    Hi unknown :)

> 	rep
> 	movw

    In my bootsector.S, it's movsw: repeat move (string) by words.
'movw' is 'mov word size operands'.

> 	jmpi	go,INITSEG

    AFAIK, the correct is 'ljmp': long jump. What kernel sources are
you seeing?. Old kernels (2.0 and I think that 2.2 too) used as86 to
do the assembling, and the syntax was like the Intel one, but with
some differences. Not quite standard, I think.

> /////////////////////////////
> 1. What assembly language used in boot.s? Intel Asm or AT&T?

    AT&T in new kernels, fully 'assembleable' with GNU as. IMHO is a
better syntax, but I don't want to feed a troll here ;)

> 2. Where is the definition of operand movw and jmpi?
> I cant find it in the Intel Manual.

    Of course, there aren't Intel syntax anyway :) I recommend you to
see the 2.4 sources for reading the assembler part. Moreover, the
info section for 'GNU as' comments the differences between Intel
assembly syntax and the AT&T one. This will be of great help.

    In addition to this, I have a document about using GNU as for
real mode assembly that comments some of these points. But it is
written in spanish only :((

    Last, the Assembly-HOWTO will cast some light to the issue, too.

    Raúl

  parent reply	other threads:[~2002-09-26 16:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-26 14:52 A newbie's question immortal1015
2002-09-26 15:22 ` jbradford
2002-09-26 16:14 ` DervishD [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-08 18:28 David Li
2015-12-08 18:48 ` Higgs, Stephen
2015-12-11 16:31   ` David Li
2015-12-11 17:07     ` Higgs, Stephen
2015-12-11 17:33       ` David Li

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020926161424.GF47@DervishD \
    --to=raul@pleyades.net \
    --cc=immortal1015@52mail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.