From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: Re: [PATCH] Windows compile errors
Date: Fri, 16 May 2008 18:16:33 +0200 [thread overview]
Message-ID: <fb249edb0805160916o1cd25f0bma88c052491b0d50d@mail.gmail.com> (raw)
In-Reply-To: <g0kb32$gut$1@ger.gmane.org>
On 16/05/2008, consul <void@aleksoft.net> wrote:
> "Johannes Schindelin" <Johannes.Schindelin@gmx.de> wrote in message
> news:alpine.DEB.1.00.0805161043540.30431@racer...
>
> > It is common to say "Sleep((x) * 1000)" to prevent errors, such as when
> > you write "sleep(1000 + 0);"
> >
>
>
> I think this may be not a right thing to do anyway. How does the sleep help
> here? does the musicpal_init run in a separate thread?
> /*
> * Wait a bit to catch menu button during U-Boot start-up
> * (to trigger emergency update).
> */
> sleep(1);
I understand this was meant to give the user time to press a key on
the keyboard after realeasing enter when running qemu from command
line, and before the emulation starts. Yes, it's hack but I merged it
because it was quite obvious and the harm from removing it is minor.
Regarding the n800 breakage, I mentioned earlier that it's broken
without a patch posted on this list. I'll try to come with something
to make it work out of the box.
Regards
next prev parent reply other threads:[~2008-05-16 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 0:04 [Qemu-devel] [PATCH] Windows compile errors consul
2008-05-16 0:15 ` Johannes Schindelin
2008-05-16 4:38 ` [Qemu-devel] " Alex
2008-05-16 9:44 ` Johannes Schindelin
2008-05-16 16:00 ` [Qemu-devel] " consul
2008-05-16 16:16 ` andrzej zaborowski [this message]
2008-05-16 16:29 ` [Qemu-devel] " Jan Kiszka
2008-05-17 2:17 ` Alex
2008-05-17 12:22 ` Jan Kiszka
2008-05-16 10:15 ` Eduardo Felipe
2008-05-16 0:38 ` [Qemu-devel] " Erik de Castro Lopo
2008-05-16 4:23 ` [Qemu-devel] " Alex
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=fb249edb0805160916o1cd25f0bma88c052491b0d50d@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).