All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/3] package/qemu: add spice support
Date: Tue, 7 Jul 2020 15:30:10 +0200	[thread overview]
Message-ID: <4578bcf3-b023-b16d-4d20-c537c380709a@gmail.com> (raw)
In-Reply-To: <CAM=7fbdQx1Ezsag--jz-RNSmxnr0zbVYz5J_xjmx=jDOs8KasA@mail.gmail.com>

Hi Jared, Thomas,

Le 29/06/2020 ? 23:05, Jared Bents a ?crit?:
> Hi Thomas,
> 
> 
> On Mon, Jun 29, 2020 at 3:59 PM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
>>
>> On Mon, 29 Jun 2020 15:50:00 -0500
>> Jared Bents <jared.bents@rockwellcollins.com> wrote:
>>
>>> update to add qemu spice support
>>>
>>> Signed-off-by: Jared Bents <jared.bents@rockwellcollins.com>
>>> ---
>>>  package/qemu/Config.in | 9 +++++++++
>>>  package/qemu/qemu.mk   | 8 +++++++-
>>>  2 files changed, 16 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/package/qemu/Config.in b/package/qemu/Config.in
>>> index 33d4cccd7b..3de73b69ec 100644
>>> --- a/package/qemu/Config.in
>>> +++ b/package/qemu/Config.in
>>> @@ -127,6 +127,15 @@ config BR2_PACKAGE_QEMU_SDL
>>>  comment "SDL frontend needs a toolchain w/ dynamic library"
>>>       depends on BR2_STATIC_LIBS
>>>
>>> +config BR2_PACKAGE_QEMU_SPICE
>>> +     bool "Enable Spice frontend"
>>> +     depends on BR2_PACKAGE_SPICE
>>
>> I am wondering why for this one we are adding a sub-option and not
>> using automatic detection of BR2_PACKAGE_SPICE=y in the .mk file, like
>> you've done for VNC and usb-redir.
>>
>> On the other hand, we do have already a bunch of sub-options to
>> configure Qemu. We're not very consistent here :/

How to enable systems emulation or user-land emulation without sub-options?
What about removing BR2_PACKAGE_QEMU_SDL and BR2_PACKAGE_QEMU_FDT options and
handle the dependencies automatically?

>>
>> Thomas
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
> 
> I based the handling of the --enable-spice option off of an old
> upstream attempt from Yann that I had found at
> http://lists.buildroot.org/pipermail/buildroot/2012-December/063058.html
> . I don't have a preference either way so let me know if you'd prefer
> a suboption or have it automatically enabled if BR2_PACKAGE_SPICE is
> enabled similarly to the other options I've added.

I guess we should enable spice only when spice package is enabled by the user
(automatic detection).

Best regards,
Romain

> 
> Thank you,
> Jared
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2020-07-07 13:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 20:50 [Buildroot] [PATCH v1 1/3] package/qemu: add spice support Jared Bents
2020-06-29 20:50 ` [Buildroot] [PATCH v1 2/3] package/qemu: add vnc support Jared Bents
2020-07-07 12:56   ` Romain Naour
2020-06-29 20:50 ` [Buildroot] [PATCH v1 3/3] package/qemu: add usb-redir support Jared Bents
2020-07-07 13:37   ` Romain Naour
2020-06-29 20:59 ` [Buildroot] [PATCH v1 1/3] package/qemu: add spice support Thomas Petazzoni
2020-06-29 21:05   ` Jared Bents
2020-07-07 13:30     ` Romain Naour [this message]
2020-07-13 21:31 ` 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=4578bcf3-b023-b16d-4d20-c537c380709a@gmail.com \
    --to=romain.naour@gmail.com \
    --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.