On 21 March 2013 18:25, Anthony Liguori wrote:
> Gerd Hoffmann writes:
>> I think the most sensible way to handle this is to implement the output
>> routing device, make it own the (single) QemuConsole, and depending on
>> the router state the one or the other display device is allowed to
>> rend
Gerd Hoffmann writes:
> Hi,
>
> If so, we're going to need to model what the hardware actually
> does, which is that there's a single connection on the back
> of the box for a monitor, and it's guest software controllable
> which of the two display devices is routed to the conne
Hi,
If so, we're going to need to model what the hardware actually
does, which is that there's a single connection on the back
of the box for a monitor, and it's guest software controllable
which of the two display devices is routed to the connection...
>>>
>>> How does this
On 21 March 2013 08:51, Gerd Hoffmann wrote:
> On 03/21/13 08:52, Gerd Hoffmann wrote:
>> On 03/20/13 21:06, Peter Maydell wrote:
>>> On 20 March 2013 09:43, Gerd Hoffmann wrote:
Multihead support: For each graphical console we'll create a gtk
window, so with multiple graphics cards in
On 03/21/13 08:52, Gerd Hoffmann wrote:
> On 03/20/13 21:06, Peter Maydell wrote:
>> On 20 March 2013 09:43, Gerd Hoffmann wrote:
>>> Multihead support: For each graphical console we'll create a gtk
>>> window, so with multiple graphics cards installed you get a gtk window
>>> for each. vte tabs
On 03/20/13 21:06, Peter Maydell wrote:
> On 20 March 2013 09:43, Gerd Hoffmann wrote:
>> Multihead support: For each graphical console we'll create a gtk
>> window, so with multiple graphics cards installed you get a gtk window
>> for each. vte tabs are attached to the console #0 window.
>
> S
On 20 March 2013 09:43, Gerd Hoffmann wrote:
> Multihead support: For each graphical console we'll create a gtk
> window, so with multiple graphics cards installed you get a gtk window
> for each. vte tabs are attached to the console #0 window.
So is this going to mean arm's vexpress-a9 gets a
On 03/20/2013 01:43 PM, Gerd Hoffmann wrote:
>
>> Multihead support: For each graphical console we'll create a gtk
>> window, so with multiple graphics cards installed you get a gtk window
>> for each. vte tabs are attached to the console #0 window.
>> ---
>> ui/gtk.c | 40 +++
On 03/20/13 14:04, Anthony Liguori wrote:
> Gerd Hoffmann writes:
>
>> Multihead support: For each graphical console we'll create a gtk
>> window, so with multiple graphics cards installed you get a gtk window
>> for each. vte tabs are attached to the console #0 window.
>
> This is neat but I'
Gerd Hoffmann writes:
> Multihead support: For each graphical console we'll create a gtk
> window, so with multiple graphics cards installed you get a gtk window
> for each. vte tabs are attached to the console #0 window.
This is neat but I'm not sure if the user experience is right.
Each win
Multihead support: For each graphical console we'll create a gtk
window, so with multiple graphics cards installed you get a gtk window
for each. vte tabs are attached to the console #0 window.
---
ui/gtk.c | 40 +++-
1 file changed, 27 insertions(+), 13 del
11 matches
Mail list logo
