mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: barebox@lists.infradead.org
Subject: [PATCH 0/2] x86 minor fixes and questions
Date: Fri,  8 Nov 2013 19:30:37 +0100	[thread overview]
Message-ID: <1383935439-23623-1-git-send-email-thomas.petazzoni@free-electrons.com> (raw)

Hello,

Here are two minor fixes for the x86 support. The first patch avoids
linking problems on recent gcc versions, and the second one fixes the
documentation.

Also, I've tested the x86 support under Qemu, it starts fine. Thanks
to the bios disk driver, it detects one hard disk drive. However,
since the driver doesn't set num_blocks, the disk size is zero, and no
partition can be detected. Is this bios disk driver supposed to work
to read the entire hard drive, access a filesystem and load the kernel
image, or is the x86 support generally too limited for this at the
moment?

Thanks,

Thomas

Thomas Petazzoni (2):
  scripts/setupmbr: fix documentation
  arch/x86: fix link with recent gcc

 arch/x86/Makefile           | 3 ++-
 scripts/setupmbr/setupmbr.c | 4 ++--
 2 files changed, 4 insertions(+), 3 deletions(-)

-- 
1.8.1.2


_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2013-11-08 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08 18:30 Thomas Petazzoni [this message]
2013-11-08 18:30 ` [PATCH 1/2] scripts/setupmbr: fix documentation Thomas Petazzoni
2013-11-08 18:30 ` [PATCH 2/2] arch/x86: fix link with recent gcc Thomas Petazzoni
2013-11-11  7:57 ` [PATCH 0/2] x86 minor fixes and questions Sascha Hauer
2013-11-11  9:50   ` Thomas Petazzoni

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=1383935439-23623-1-git-send-email-thomas.petazzoni@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=barebox@lists.infradead.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