public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Martin Mares <mj@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86 Boot enhancements, pic 16 4/9
Date: 05 Apr 2002 02:44:09 -0700	[thread overview]
Message-ID: <m1bscypjiu.fsf@frodo.biederman.org> (raw)
In-Reply-To: <m11ydwu5at.fsf@frodo.biederman.org> <20020405080115.GA409@ucw.cz> <m1k7rmpmyq.fsf@frodo.biederman.org> <20020405084733.GG609@ucw.cz> <m1g02aplmm.fsf@frodo.biederman.org> <20020405090846.GL609@ucw.cz>

Martin Mares <mj@ucw.cz> writes:

> Hello!
> 
> > Show me a linker script that can link together bootsect.o and bsetup.o.
> 
> I don't have enough time to experiment with it at this very moment
> and I admit that the linker bugs you've mentioned make it impossible,
> but the objdump solution I mentioned (and tried a couple of minutes ago)
> works and although it isn't perfect, it's lovely compared to the
> "-start" hack.

Given that I want a relative offset, and I have explicitly coded a
relative offset, I don't see how that is a hack.  I see assembly
for is telling the machine explicitly what to do and that does.

The fact the correct way to code the instruction looks ugly is a gas
bug/deficiency.  Perhaps a gas developer will look at how ugly that
code is and improve gas.

One of the other reasons I want to do it this way is in case is to
make copying code easier.  If you use idioms that work equally well
everywhere and for every case it is easier to switch between projects
using the same tool.  And the assume 0 hack isn't useful when
switching from real to protected mode while using the code segment
you got from the reset vector.  Although it is kind of fun running
real mode code with a code segment base of 0xffff0000.

Eric

  reply	other threads:[~2002-04-05  9:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-03 16:15 [PATCH] x86 Boot enhancements, pic 16 4/9 Eric W. Biederman
2002-04-03 19:40 ` H. Peter Anvin
2002-04-04  2:54   ` Eric W. Biederman
2002-04-05  8:01 ` Martin Mares
2002-04-05  8:29   ` Eric W. Biederman
2002-04-05  8:47     ` Martin Mares
2002-04-05  8:58       ` Eric W. Biederman
2002-04-05  9:08         ` Martin Mares
2002-04-05  9:44           ` Eric W. Biederman [this message]
2002-04-05 10:59             ` Martin Mares
2002-04-05 16:24               ` Maciej W. Rozycki
2002-04-05 20:59               ` Eric W. Biederman

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=m1bscypjiu.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox