All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Hentschel" <nerv@dawncrow.de>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot for normal PC
Date: Sat, 20 Feb 2016 14:45:55 +0100	[thread overview]
Message-ID: <56C86E13.8040203@dawncrow.de> (raw)
In-Reply-To: <20160220101054.GA3418@free.fr>

Am 20.02.2016 um 11:10 schrieb Yann E. MORIN:
> Andr?, All,
>

Hi,

Thanks for the hints.
But I really need bare metal for my intents, qemu won't help.
As soon as I have more time I'll try, if I succeed I'll also try to upstream a defconfig.

> On 2016-02-19 23:53 +0100, Andr? Hentschel spake thusly:
>> I wanna try some more things with the Wine package in buildroot, but I
>> can't easily setup a testing environment for a PC.
> 
>     $ make list-defconfigs |grep x86
>       qemu_x86_64_defconfig               - Build for qemu_x86_64
>       qemu_x86_defconfig                  - Build for qemu_x86
> 
> So I'd suggest you use qemu for that.
> 
>> One part is which bootloader to use and how to pack everything together
>> to a bootable USB-Stick, HDD image or CD. (And I didn't found a defconfig
>> for that)...
> 
> No, we don't have a defconfig for a traditional PC.
> 
>> The other part is about the nvidia-driver, I'll need the legacy one for
>> my card. Can I simply alter the version number in the makefile?
> 
> I'm not sure the legacy driver has the same "layout" (in terms of
> buildsystem) as the current driver, so I would not bet on it...
> 
> However, if as I suggested above, you were to use qemu, you would not
> need to setup a bootloader. You can tell qemu to directly boot a kernel,
> see:
>     board/qemu/x86/readme.txt
> 
> As for the video driver, qemu does not (yet!) provide a 3D-accelerated
> graphics card, but you can use mesa3d for SW OpenGL if you need that.
> 
> I guess using qemu will be more efficient than using a real PC, at least
> as long as you're not looking at performance, and especially graphics
> performance.
> 
> Well, at least, that's what I would be doing. ;-)
> 
> Regards,
> Yann E. MORIN.
> 

  reply	other threads:[~2016-02-20 13:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-19 22:53 [Buildroot] Buildroot for normal PC André Hentschel
2016-02-20 10:10 ` Yann E. MORIN
2016-02-20 13:45   ` André Hentschel [this message]
2016-02-20 23:42 ` Arnout Vandecappelle
2016-02-23 20:26   ` André Hentschel
2016-02-24 20:36     ` Arnout Vandecappelle

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=56C86E13.8040203@dawncrow.de \
    --to=nerv@dawncrow.de \
    --cc=buildroot@busybox.net \
    /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.