Hi,
> What are the required semantics for update/switch/refresh?
> These don't seem to be documented. Can we validly make
> those be asychronous, or does the midlayer require that
> the operation has completed and been reflected onscreen
> before the update/switch/refresh callback returns ?
re
On Thu, 22 Nov 2018 at 07:32, Gerd Hoffmann wrote:
>
> Hi,
>
> > Something somewhere in this call chain should have taken
> > the iothread lock, I assume, but I'm not sure where.
> >
> > Gerd -- what are the rules of the UI subsystem regarding
> > multiple threads, and what threads are allowed t
Hi,
> Something somewhere in this call chain should have taken
> the iothread lock, I assume, but I'm not sure where.
>
> Gerd -- what are the rules of the UI subsystem regarding
> multiple threads, and what threads are allowed to call
> UI functions like qemu_input_event_send_key_qcode(),
> fr
(Hi Gerd -- I have a question at the bottom of this email
about the thread/locking semantics of the UI midlayer...)
On 20 November 2018 at 12:59, Peter Maydell wrote:
> On 11 November 2018 at 21:24, Berkus Decker wrote:
>> It seems that Cocoa checks are stricter on Mojave and some callbacks that
On Wed, Nov 21, 2018 at 05:53:50AM -0500, Programmingkid wrote:
>
> > On 13 November 2018 at 12:12, Programmingkid
> > wrote:
> >>> On Nov 11, 2018, at 4:35 PM, Berkus Decker wrote:
> >>> These changes are ought to work on OSX 10.6, although I don?t have a
> >>> machine handy to test it.
> >>
> On 13 November 2018 at 12:12, Programmingkid
> wrote:
>>> On Nov 11, 2018, at 4:35 PM, Berkus Decker wrote:
>>> These changes are ought to work on OSX 10.6, although I don?t have a
>>> machine handy to test it.
>>
>> I have Mac OS 10.6 available for testing.
>
> This is perhaps a good poin
On Tue, Nov 20, 2018 at 01:09:54PM +, Peter Maydell wrote:
> On 13 November 2018 at 12:12, Programmingkid
> wrote:
> >> On Nov 11, 2018, at 4:35 PM, Berkus Decker wrote:
> >> These changes are ought to work on OSX 10.6, although I don?t have a
> >> machine handy to test it.
> >
> > I have Ma
On 13 November 2018 at 12:12, Programmingkid wrote:
>> On Nov 11, 2018, at 4:35 PM, Berkus Decker wrote:
>> These changes are ought to work on OSX 10.6, although I don?t have a machine
>> handy to test it.
>
> I have Mac OS 10.6 available for testing.
This is perhaps a good point to ask the ques
On 11 November 2018 at 21:24, Berkus Decker wrote:
> It seems that Cocoa checks are stricter on Mojave and some callbacks that
> worked from non-GUI thread on High Sierra are no longer working.
>
> The fixes included here are:
>
> * Deferring qemu_main() to another thread so that the actual main
I will double check on High Sierra and El Capitan.
So far I only tested qemu-system-aarch64 and it worked on Mojave, but did not
test elsewhere (my aim was to get my osdev going, only).
I have a range of older osx machines (not as old as 10.6 though), so will put
it through some rounds. Will po
> On Nov 11, 2018, at 4:35 PM, qemu-devel-requ...@nongnu.org wrote:
>
> It seems that Cocoa checks are stricter on Mojave and some callbacks that
> worked from non-GUI thread on High Sierra are no longer working.
>
> The fixes included here are:
>
> * Deferring qemu_main() to another thread s
> On Nov 11, 2018, at 4:35 PM, qemu-devel-requ...@nongnu.org wrote:
>
> It seems that Cocoa checks are stricter on Mojave and some callbacks that
> worked from non-GUI thread on High Sierra are no longer working.
>
> The fixes included here are:
>
> * Deferring qemu_main() to another thread s
It seems that Cocoa checks are stricter on Mojave and some callbacks that
worked from non-GUI thread on High Sierra are no longer working.
The fixes included here are:
* Deferring qemu_main() to another thread so that the actual main thread is
reserved for the Cocoa UI; it also removes blocking
13 matches
Mail list logo
