qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: seabios <seabios@seabios.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [SeaBIOS] Boot failure with MS-Dos 6.22 (due to bad BIOS	build?)
Date: Mon, 27 Feb 2012 17:20:11 +0100	[thread overview]
Message-ID: <20120227162012.977.qmail@stuge.se> (raw)
In-Reply-To: <4F4BAB10.5020409@siemens.com>

Jan Kiszka wrote:
> Well, the Linux kernel can also be built with practically any distro
> out there.

Yeah. Maybe that gets tested more than building coreboot and SeaBIOS,
and so problems are discovered by those who introduce them.


> Having a need for a separate toolchain for building x86 on x86 is
> a bit overkill IMHO, at least for someone hacking on Seabios only
> infrequently like /me.

OTOH it takes about 20 minutes to build a toolchain on a reasonably
fast machine, and the script makes it quite effortless.


> PS: Please avoid "mail-followup-to" in your replies, it messes up To/CC.

Moved this discussion to private email.


//Peter

  reply	other threads:[~2012-02-27 16:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27  9:51 [Qemu-devel] Boot failure with MS-Dos 6.22 (due to bad BIOS build?) Daniel P. Berrange
2012-02-27 15:25 ` Jan Kiszka
2012-02-27 16:00   ` [Qemu-devel] [SeaBIOS] " Peter Stuge
2012-02-27 16:10     ` Jan Kiszka
2012-02-27 16:20       ` Peter Stuge [this message]
2012-02-29  8:45   ` [Qemu-devel] " Kevin O'Connor
2012-02-29  9:19     ` Daniel P. Berrange
2012-02-29  9:51       ` [Qemu-devel] [SeaBIOS] " Fred .
2012-03-19  0:29   ` [Qemu-devel] " Kevin O'Connor
2012-03-19 20:03     ` Jan Kiszka
2012-03-20  2:17       ` Kevin O'Connor

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=20120227162012.977.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).