All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bogdan <love4boobies@yahoo.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: 16-bit bootloader support?
Date: Fri, 9 Oct 2009 06:37:45 -0700 (PDT)	[thread overview]
Message-ID: <970783.94976.qm@web37104.mail.mud.yahoo.com> (raw)
In-Reply-To: <ad2655cb0910090606x6c965ec0md6784693c0bdac2c@mail.gmail.com>

Well yes, that's exactly what this discussion was about, wasn't it? :)

Cheers,
Bogdan




----- Original Message ----
From: James Courtier-Dutton <james.dutton@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Sent: Fri, October 9, 2009 4:06:45 PM
Subject: Re: 16-bit bootloader support?

2009/10/7 Gabe Black <Gabe.Black@ni.com>:
>
> So I have a real-time OS named Pharlap that has a 16-bit bootloader that
> ends up switching to 32-bit protected mode and loads the OS.  I think it
> relies on the first sector of the partition being loaded and execution
> simply started - but in real-mode.
>
> Is there any way to have grub do this (legacy or grub2)?  I tried
> chainloading, but I think that may be loading it in 32-bit mode.  Any
> pointers on what code I would have to modify to create that option for grub?
>
> Any help is appreciated.
>

I don't think grub can work on any CPU below a 80386.
It probably will no work on 8086, 80186 and 80286.


_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel



      



      reply	other threads:[~2009-10-09 13:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07 19:26 16-bit bootloader support? Gabe Black
2009-10-07 20:12 ` Felix Zielcke
2009-10-07 20:22 ` Vladimir 'phcoder' Serbinenko
2009-10-08  5:34 ` Bogdan
2009-10-08 12:28   ` Vladimir 'phcoder' Serbinenko
2009-10-09 13:06 ` James Courtier-Dutton
2009-10-09 13:37   ` Bogdan [this message]

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=970783.94976.qm@web37104.mail.mud.yahoo.com \
    --to=love4boobies@yahoo.com \
    --cc=grub-devel@gnu.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.