Re: Help improve 32-bit testing

2024-06-25 Thread Alex Bennée
Richard Henderson writes: > Hiya, > > I've just discovered a 32-bit build issue that is probably 3 weeks old. > > While we still support 32-bit builds at all, I would request that we > improve our cross-i686 testing. For instance: we have cross-i686-user > and cross-i686-tci. There is some syst

Re: Help improve 32-bit testing

2024-06-25 Thread Richard Henderson
On 6/25/24 00:57, Philippe Mathieu-Daudé wrote: Hi Richard, On 25/6/24 01:33, Richard Henderson wrote: Hiya, I've just discovered a 32-bit build issue that is probably 3 weeks old. How and what did you notice? https://lore.kernel.org/qemu-devel/91f19b8d-387a-47cd-b7cc-19cdf4442...@linaro.o

Re: Help improve 32-bit testing

2024-06-25 Thread Richard Henderson
On 6/25/24 00:11, Thomas Huth wrote: On 25/06/2024 01.33, Richard Henderson wrote: Hiya, I've just discovered a 32-bit build issue that is probably 3 weeks old. While we still support 32-bit builds at all, I would request that we improve our cross-i686 testing.  For instance: we have cross-i6

Re: Help improve 32-bit testing

2024-06-25 Thread Philippe Mathieu-Daudé
Hi Richard, On 25/6/24 01:33, Richard Henderson wrote: Hiya, I've just discovered a 32-bit build issue that is probably 3 weeks old. How and what did you notice? While we still support 32-bit builds at all, I would request that we improve our cross-i686 testing.  For instance: we have cross

Re: Help improve 32-bit testing

2024-06-25 Thread Daniel P . Berrangé
On Mon, Jun 24, 2024 at 04:33:08PM -0700, Richard Henderson wrote: > Hiya, > > I've just discovered a 32-bit build issue that is probably 3 weeks old. > > While we still support 32-bit builds at all, I would request that we improve > our cross-i686 testing. For instance: we have cross-i686-user

Re: Help improve 32-bit testing

2024-06-25 Thread Thomas Huth
On 25/06/2024 01.33, Richard Henderson wrote: Hiya, I've just discovered a 32-bit build issue that is probably 3 weeks old. While we still support 32-bit builds at all, I would request that we improve our cross-i686 testing.  For instance: we have cross-i686-user and cross-i686-tci.  There is

Re: Help understanding allocation and mapping flow of virtio-gpu 3D resource blobs

2024-02-04 Thread Alex Bennée
Alex Bennée writes: (doh, replying to virglrender-devel thanks to autocomplete failure) > Hi, > > I'm trying to get an understanding of the blob allocation and mapping > flow for virtio-gpu for Vulkan and Rutabaga. Having gotten all the > various libraries setup I'm still seeing failures when ru

Re: Help understanding allocation and mapping flow of virtio-gpu 3D resource blobs

2024-02-04 Thread Manos Pitsidianakis
Good morning Alex, Just one observation, On Sun, 04 Feb 2024 13:06, Alex Bennée wrote: Hi, I'm trying to get an understanding of the blob allocation and mapping flow for virtio-gpu for Vulkan and Rutabaga. Having gotten all the various libraries setup I'm still seeing failures when running a

Re: Help wanted for enabling -Wshadow=local

2023-09-25 Thread Warner Losh
On Sat, Sep 23, 2023 at 6:33 AM Peter Maydell wrote: > On Fri, 22 Sept 2023 at 19:59, Warner Losh wrote: > > The third one, though, makes me ask the question: When should we > > pass in cpu_env to functions and when should we use the global value? > > > > I have a lot of changes that look like:

Re: Help wanted for enabling -Wshadow=local

2023-09-23 Thread Peter Maydell
On Fri, 22 Sept 2023 at 19:59, Warner Losh wrote: > The third one, though, makes me ask the question: When should we > pass in cpu_env to functions and when should we use the global value? > > I have a lot of changes that look like: > > -static inline abi_long do_freebsd_thr_exit(CPUArchState *cpu

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Warner Losh
On Fri, Sep 22, 2023 at 11:49 AM Peter Maydell wrote: > On Fri, 22 Sept 2023 at 18:43, Daniel Henrique Barboza > wrote: > > Can you publish your branch with the current -Wshadow=local patches in > > gitlab/github? I'm hitting (and fixing) a lot of errors that aren't > listed > > here, meaning th

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Peter Maydell
On Fri, 22 Sept 2023 at 18:43, Daniel Henrique Barboza wrote: > Can you publish your branch with the current -Wshadow=local patches in > gitlab/github? I'm hitting (and fixing) a lot of errors that aren't listed > here, meaning they're either fixed already in your local branch or needs to > be fix

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Ani Sinha
> On 22-Sep-2023, at 3:07 PM, Markus Armbruster wrote: > > X86 Machines > > PC > M: Michael S. Tsirkin > M: Marcel Apfelbaum >hw/i386/acpi-build.c(*3*) >hw/i386/acpi-microvm.c(*2*) >hw/i386/intel_iommu.c(*3*) >hw/i386/pc.c(*2*) >hw/i386/x86.c(*2*) Since I al

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Peter Maydell
On Fri, 22 Sept 2023 at 10:37, Markus Armbruster wrote: > > If you are in To:, we need your help to enable -Wshadow=local. > > Local variables shadowing other local variables or parameters make the > code needlessly hard to understand. Bugs love to hide in such code. > Evidence: "[PATCH v3 1/7] m

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Markus Armbruster
"Michael S. Tsirkin" writes: > On Fri, Sep 22, 2023 at 04:03:27PM +0530, Ani Sinha wrote: >> >> >> > On 22-Sep-2023, at 3:07 PM, Markus Armbruster wrote: >> > >> > Devices >> > --- >> > ACPI/SMBIOS >> > M: Michael S. Tsirkin >> > M: Igor Mammedov >> > R: Ani Sinha >> >hw/acpi/cpu_h

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Michael S. Tsirkin
On Fri, Sep 22, 2023 at 04:03:27PM +0530, Ani Sinha wrote: > > > > On 22-Sep-2023, at 3:07 PM, Markus Armbruster wrote: > > > > Devices > > --- > > ACPI/SMBIOS > > M: Michael S. Tsirkin > > M: Igor Mammedov > > R: Ani Sinha > >hw/acpi/cpu_hotplug.c > >hw/i386/acpi-build.c(*3*) >

Re: Help wanted for enabling -Wshadow=local

2023-09-22 Thread Ani Sinha
> On 22-Sep-2023, at 3:07 PM, Markus Armbruster wrote: > > Devices > --- > ACPI/SMBIOS > M: Michael S. Tsirkin > M: Igor Mammedov > R: Ani Sinha >hw/acpi/cpu_hotplug.c >hw/i386/acpi-build.c(*3*) >hw/smbios/smbios.c I will look into this after enabling diff --git a/meson.bu

Re: Help with QEMU DBUS display

2023-08-27 Thread Marc-André Lureau
Hi On Mon, Aug 28, 2023 at 7:58 AM Elijah R wrote: > > Hi! > > I'm currently attempting to use qemu's DBUS display from within a go > application, using the godbus library. However, I'm hitting some roadblocks, > and this is probably because I'm a bit confused about how qemu's peer-to-peer > d

Re: Help finding Coverity defects for generated Hexagon code

2023-06-02 Thread Anton Johansson via
On 5/23/23 19:56, Brian Cain wrote: -Original Message- From: qemu-devel-bounces+bcain=quicinc@nongnu.org On Behalf Of Richard Henderson Sent: Tuesday, May 23, 2023 10:32 AM To: a...@rev.ng; Paolo Bonzini ; Peter Maydell Cc: qemu-devel@nongnu.org Subject: Re: Help finding

RE: Help finding Coverity defects for generated Hexagon code

2023-05-23 Thread Brian Cain
> -Original Message- > From: qemu-devel-bounces+bcain=quicinc@nongnu.org bounces+bcain=quicinc@nongnu.org> On Behalf Of Richard Henderson > Sent: Tuesday, May 23, 2023 10:32 AM > To: a...@rev.ng; Paolo Bonzini ; Peter Maydell > > Cc: qemu-devel@nongnu.or

Re: Help finding Coverity defects for generated Hexagon code

2023-05-23 Thread Richard Henderson
On 5/23/23 06:29, Anton Johansson via wrote: On 5/23/23 12:29, Paolo Bonzini wrote: On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote: On Mon, 22 May 2023 at 21:24, Anton Johansson wrote: Hi, coverity recently reported some defects in code generated by idef-parser (email attached). Thes

Re: Help finding Coverity defects for generated Hexagon code

2023-05-23 Thread Anton Johansson via
On 5/23/23 12:29, Paolo Bonzini wrote: On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote: On Mon, 22 May 2023 at 21:24, Anton Johansson wrote: Hi, coverity recently reported some defects in code generated by idef-parser (email attached). These defects are expected and we plan to emit a

Re: Help finding Coverity defects for generated Hexagon code

2023-05-23 Thread Paolo Bonzini
On Tue, May 23, 2023 at 11:18 AM Peter Maydell wrote: > On Mon, 22 May 2023 at 21:24, Anton Johansson wrote: > > Hi, > > > > coverity recently reported some defects in code generated by idef-parser > > (email attached). These defects are expected and we plan to emit a > > /* coverity[event_tag] *

Re: Help finding Coverity defects for generated Hexagon code

2023-05-23 Thread Peter Maydell
On Mon, 22 May 2023 at 21:24, Anton Johansson wrote: > > Hi, > > coverity recently reported some defects in code generated by idef-parser > (email attached). These defects are expected and we plan to emit a > /* coverity[event_tag] */ comment to disable the specific event triggered. We don't mark

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-06-06 Thread Cédric Le Goater
On 6/6/22 19:02, Peter Maydell wrote: On Mon, 6 Jun 2022 at 16:37, Cédric Le Goater wrote: On the CPU topic, I think we will need to change the GIC device to stop using qemu_get_cpu() in the CPU interface init routine and in the GIC realize routine, since this is global to the machine. I am hav

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-06-06 Thread Peter Maydell
On Mon, 6 Jun 2022 at 16:37, Cédric Le Goater wrote: > On the CPU topic, I think we will need to change the GIC device > to stop using qemu_get_cpu() in the CPU interface init routine > and in the GIC realize routine, since this is global to the machine. > I am having the same problem when trying

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-06-06 Thread Cédric Le Goater
Hello Peter M., [ ... ] Another device that does some moderately complicated things with MemoryRegions is the hw/arm/armsse.c SoC, which has several CPUs and has some per-CPU devices. I think we have not thus far had a model of a board where different CPUs see radically different things (only

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-05-30 Thread Peter Delevoryas
> On May 30, 2022, at 11:15 AM, Cédric Le Goater wrote: > > On 5/30/22 18:53, Peter Maydell wrote: >> On Thu, 26 May 2022 at 23:14, Peter Delevoryas wrote: >>> Hey QEMU developers, >>> >>> Cedric mentioned here[1] that QEMU can support emulating a >>> more complete board, e.g. a machine with

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-05-30 Thread Cédric Le Goater
On 5/30/22 18:53, Peter Maydell wrote: On Thu, 26 May 2022 at 23:14, Peter Delevoryas wrote: Hey QEMU developers, Cedric mentioned here[1] that QEMU can support emulating a more complete board, e.g. a machine with an AST2600 *and* an AST1030. This is true, as long as all the CPUs are the sam

Re: Help: How do I make a machine with 2 separate ARM SoC's?

2022-05-30 Thread Peter Maydell
On Thu, 26 May 2022 at 23:14, Peter Delevoryas wrote: > Hey QEMU developers, > > Cedric mentioned here[1] that QEMU can support emulating a > more complete board, e.g. a machine with an AST2600 *and* an AST1030. This is true, as long as all the CPUs are the same architecture family, e.g. all Arm

Re: Help with ppc e500 tlb usage

2022-01-21 Thread Jesse Millwood
On Fri, 2022-01-21 at 13:17 +0100, Cédric Le Goater wrote: > Hello Jesse, > > ( For some reason, your email never reached my mailbox. In the > future, >    could please also Cc: mailto:qemu-devel@nongnu.org. ) > Absolutely, I wasn't sure how much posting to two mailing lists was accepted. > On

Re: [EXT] - Re: Help with ppc e500 tlb usage

2022-01-21 Thread Jesse Millwood
On Fri, 2022-01-21 at 18:57 +0100, Cédric Le Goater wrote: > CAUTION: This email originated from outside of the organization. > Please do not click links or open attachments unless you recognize > the sender's email address and know the content is safe. > > > > Thanks for the background info Cédr

Re: Help with ppc e500 tlb usage

2022-01-21 Thread Cédric Le Goater
Thanks for the background info Cédric, I wasn't aware of the MMUv2. I see now that in target/ppc/cpu_init.c the e500v2 and e5500 have the same mmu_model, the POWREPC_MMU_BOOKE206. I'd like to be able to set the initial tlb entry size from the platform definition by indicating the size in kib. I

Re: Help with ppc e500 tlb usage

2022-01-21 Thread Cédric Le Goater
Hello Jesse, ( For some reason, your email never reached my mailbox. In the future, could please also Cc: qemu-devel@nongnu.org. ) On 1/18/22 20:40, Jesse Millwood wrote: Hello, I'm trying to get the e500 to set the initial tlb entry to mirror what the platform expects. I have made some cha

Re: Help adding package to gitlab runners

2021-09-13 Thread Jag Raman
> On Sep 13, 2021, at 1:38 AM, Thomas Huth wrote: > > On 13/09/2021 03.14, Jag Raman wrote: >> Hi, >> I'm wondering about the best way to install a dependency package on >> GitLab runners. >> >> I'm adding libvfio-user [1] as a submodule to QEMU. libvfio-user depends >> on the availability of

Re: Help adding package to gitlab runners

2021-09-12 Thread Thomas Huth
On 13/09/2021 03.14, Jag Raman wrote: Hi, I'm wondering about the best way to install a dependency package on GitLab runners. I'm adding libvfio-user [1] as a submodule to QEMU. libvfio-user depends on the availability of the "json-c" package. As such, we need to install this package to build t

Re: Help with patch

2021-07-05 Thread Peter Maydell
On Mon, 5 Jul 2021 at 14:29, Programmingkid wrote: > > Hi, I made a patch that adds an icon to QEMU on Mac OS. Who should I send > this patch to? > > > From 45650a7f52deb8c2c436d71a3fcf5326287c2e05 Mon Sep 17 00:00:00 2001 > From: John Arbuckle > Date: Tue, 2 Feb 2021 08:35:43 -0500 > Subject: [

Re: Help with Windows XP in qemu-system-i386

2021-02-10 Thread Programmingkid
> On Feb 5, 2021, at 4:08 PM, Programmingkid wrote: > > > >> On Feb 5, 2021, at 3:49 PM, Michael S. Tsirkin wrote: >> >> On Fri, Feb 05, 2021 at 03:25:00PM -0500, Programmingkid wrote: >>> Hi, I'm noticing that my Windows XP Service Pack 3 VM is causing >>> qemu-system-i386 to experience

Re: Help with Windows XP in qemu-system-i386

2021-02-07 Thread Michael S. Tsirkin
On Fri, Feb 05, 2021 at 04:08:26PM -0500, Programmingkid wrote: > > > > On Feb 5, 2021, at 3:49 PM, Michael S. Tsirkin wrote: > > > > On Fri, Feb 05, 2021 at 03:25:00PM -0500, Programmingkid wrote: > >> Hi, I'm noticing that my Windows XP Service Pack 3 VM is causing > >> qemu-system-i386 to e

Re: Help with Windows XP in qemu-system-i386

2021-02-05 Thread Programmingkid
> On Feb 5, 2021, at 3:49 PM, Michael S. Tsirkin wrote: > > On Fri, Feb 05, 2021 at 03:25:00PM -0500, Programmingkid wrote: >> Hi, I'm noticing that my Windows XP Service Pack 3 VM is causing >> qemu-system-i386 to experience 100% host cpu usage even when the guest is at >> idle. I was wonde

Re: help with a build-user and build-user-plugin failure

2020-12-03 Thread Alex Bennée
Claudio Fontana writes: > Hi all, > > and thanks for the help, after a lot of fiddling and applying your > suggestions (and a reboot !?) > now things work. > > The only thing I am left seeing (also on master) is with check-tcg: > > > Remote 'g' packet reply is too long (expected 312 bytes, got

Re: help with a build-user and build-user-plugin failure

2020-12-03 Thread Claudio Fontana
Hi all, and thanks for the help, after a lot of fiddling and applying your suggestions (and a reboot !?) now things work. The only thing I am left seeing (also on master) is with check-tcg: Remote 'g' packet reply is too long (expected 312 bytes, got 560 bytes): 00

Re: help with a build-user and build-user-plugin failure

2020-11-25 Thread Claudio Fontana
On 11/25/20 6:02 PM, Alex Bennée wrote: > > Claudio Fontana writes: > >> Hi Alex, >> >> On 11/25/20 10:42 AM, Alex Bennée wrote: >>> >>> Philippe Mathieu-Daudé writes: >>> On 11/24/20 12:04 PM, Claudio Fontana wrote: > Hi Alex, > > I am seeing build failures with build-user and

Re: help with a build-user and build-user-plugin failure

2020-11-25 Thread Alex Bennée
Claudio Fontana writes: > Hi Alex, > > On 11/25/20 10:42 AM, Alex Bennée wrote: >> >> Philippe Mathieu-Daudé writes: >> >>> On 11/24/20 12:04 PM, Claudio Fontana wrote: Hi Alex, I am seeing build failures with build-user and build-user-plugin: https://gitlab.com/hw-c

Re: help with a build-user and build-user-plugin failure

2020-11-25 Thread Claudio Fontana
Hi Alex, On 11/25/20 10:42 AM, Alex Bennée wrote: > > Philippe Mathieu-Daudé writes: > >> On 11/24/20 12:04 PM, Claudio Fontana wrote: >>> Hi Alex, >>> >>> I am seeing build failures with build-user and build-user-plugin: >>> >>> https://gitlab.com/hw-claudio/qemu/-/pipelines/220245998 >>> >>>

Re: help with a build-user and build-user-plugin failure

2020-11-25 Thread Alex Bennée
Philippe Mathieu-Daudé writes: > On 11/24/20 12:04 PM, Claudio Fontana wrote: >> Hi Alex, >> >> I am seeing build failures with build-user and build-user-plugin: >> >> https://gitlab.com/hw-claudio/qemu/-/pipelines/220245998 >> >> and I am trying to start investigating. >> >> How do I repro

Re: help with a build-user and build-user-plugin failure

2020-11-24 Thread Claudio Fontana
On 11/24/20 2:54 PM, Philippe Mathieu-Daudé wrote: > On 11/24/20 12:04 PM, Claudio Fontana wrote: >> Hi Alex, >> >> I am seeing build failures with build-user and build-user-plugin: >> >> https://gitlab.com/hw-claudio/qemu/-/pipelines/220245998 >> >> and I am trying to start investigating. >> >> Ho

Re: help with a build-user and build-user-plugin failure

2020-11-24 Thread Philippe Mathieu-Daudé
On 11/24/20 12:04 PM, Claudio Fontana wrote: > Hi Alex, > > I am seeing build failures with build-user and build-user-plugin: > > https://gitlab.com/hw-claudio/qemu/-/pipelines/220245998 > > and I am trying to start investigating. > > How do I reproduce this locally? > > I am trying to run loc

RE: Help on TCG asserts

2020-11-02 Thread Sai Pavan Boddu
Hi Richard, > -Original Message- > From: Richard Henderson > Sent: Wednesday, October 28, 2020 8:16 PM > To: Sai Pavan Boddu ; QEMU Developers de...@nongnu.org> > Cc: Peter Maydell ; Philippe Mathieu-Daudé > > Subject: Re: Help on TCG asserts > > On 10/

Re: Help on TCG asserts

2020-10-28 Thread Richard Henderson
On 10/27/20 9:15 PM, Sai Pavan Boddu wrote: > 336 static void set_jmp_reset_offset(TCGContext *s, int which) > 337 { > 338 size_t off = tcg_current_code_size(s); > 339 s->tb_jmp_reset_offset[which] = off; > 340 /* Make sure that we did

Re: Help with usb-host hostdevice property

2020-08-27 Thread Diego Viola
On Thu, Aug 27, 2020 at 5:01 AM Gerd Hoffmann wrote: > > Hi, > > > usb 1-1: Invalid ep0 maxpacket: 64 > > usb usb1-port1: unable to enumerate USB device > > https://patchwork.ozlabs.org/project/qemu-devel/patch/20200826145239.6077-18-kra...@redhat.com/ That helps indeed, thanks Gerd! Tested-by

Re: Help with usb-host hostdevice property

2020-08-27 Thread Gerd Hoffmann
Hi, > usb 1-1: Invalid ep0 maxpacket: 64 > usb usb1-port1: unable to enumerate USB device https://patchwork.ozlabs.org/project/qemu-devel/patch/20200826145239.6077-18-kra...@redhat.com/ HTH, Gerd

Re: Help

2020-03-25 Thread Philippe Mathieu-Daudé
Hi Chained, On 3/24/20 11:13 AM, Chained Up wrote: Please can some explain what should i do here? You might have sent your question to a wrong list (this list is about QEMU: https://www.qemu.org/).  Prepare import-libraries using Borland's implib program.  The ".lib"     files that it us

[Qemu-devel] [Bug 1721744] Re: Help content missing for newly added machine properties

2017-10-06 Thread Greg Kurz
** Changed in: qemu Status: New => Invalid -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1721744 Title: Help content missing for newly added machine properties Status in QEMU: Invalid Bu

Re: [Qemu-devel] [Bug 1721744] Re: Help content missing for newly added machine properties

2017-10-06 Thread Cornelia Huck
On Fri, 06 Oct 2017 11:21:08 - Greg Kurz wrote: > Hmm... -h is common to all targets, ie, you should only find properties > that can be passed to -machine for all qemu-system-* binaries (I don't > know how s390-squash-mcss landed there but it looks wrong). That output comes from qemu-options

[Qemu-devel] [Bug 1721744] Re: Help content missing for newly added machine properties

2017-10-06 Thread Greg Kurz
Hmm... -h is common to all targets, ie, you should only find properties that can be passed to -machine for all qemu-system-* binaries (I don't know how s390-squash-mcss landed there but it looks wrong). The right way to query properties supported by a pseries machine type is: $ ./ppc64-softmmu/qe

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2010-01-04 Thread Dejun.Liu
Hi, I will do it tomorrow! sorry for that ,today i prepare for a ppt for my boss. sorry Steven Liu On Mon, 2010-01-04 at 15:17 +0700, Mulyadi Santosa wrote: > On Mon, Jan 4, 2010 at 3:10 PM, Dejun.Liu wrote: > >> > >> I will land a fix in a second. What you want to change in > > libsdl-native

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2010-01-04 Thread Dejun.Liu
Hi, OE's Holger has patch OE with this problem --- > On Monday 04 January 2010 04:11:33 Dejun.Liu wrote: > > -->I used the OE build Qemu which at the staging > > dir(angstrom-dev/staging/i686-linux/usr/bin). > > and i executed the command in the buildserver not using ssh > > The

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2010-01-04 Thread Mulyadi Santosa
On Mon, Jan 4, 2010 at 3:10 PM, Dejun.Liu wrote: >> >> I will land a fix in a second. What you want to change in > libsdl-native as >>  a quick solution is to add DEPENDS += "libx11-native" and change >>  --disable- video-x11" to --enable-video-x11". > > I(Holger) have comitted two patches for it

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2010-01-03 Thread Mulyadi Santosa
On Mon, Jan 4, 2010 at 8:06 AM, Dejun.Liu wrote: > Hi > > yes, I hava find that OE build SDL not support x11 ,so hava the error > No available video device. > > thanks all these helps Glad you spot the error. Let us know how you solve it further. Or maybe you'll be kind enough and post your howt

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2010-01-03 Thread Dejun.Liu
Hi yes, I hava find that OE build SDL not support x11 ,so hava the error No available video device. thanks all these helps Steven Liu On Thu, 2009-12-31 at 13:30 +0100, Andreas Färber wrote: > Hi, > > Am 31.12.2009 um 09:45 schrieb Dejun.Liu: > > > r...@dejunliu-desktop:/home/protocol/study/

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-31 Thread Andreas Färber
Hi, Am 31.12.2009 um 09:45 schrieb Dejun.Liu: r...@dejunliu-desktop:/home/protocol/study/OE/build# qemu-system-arm -M versatilepb -usb -usbdevice wacom-tablet -show-cursor -m 64 -kernel /home/protocol/study/OE/angstrom-dev/deploy/glibc/images/ qemuarm/zImage-2.6.25+2.6.26-rc4-r6-qemuarm.bin

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-31 Thread Dejun.Liu
Hi, I hava patched sdl.c file. return error is below: r...@dejunliu-desktop:/home/protocol/study/OE/build# qemu-system-arm -M versatilepb -usb -usbdevice wacom-tablet -show-cursor -m 64 -kernel /home/protocol/study/OE/angstrom-dev/deploy/glibc/images/qemuarm/zImage-2.6.25+2.6.26-rc4-r6-qemuarm.

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-30 Thread Michael S. Tsirkin
On Sun, Dec 27, 2009 at 05:35:56AM -0300, Dejun.Liu wrote: > Hi, > > below is my DISPLAY info: > echo ${DISPLAY} > :0.0 > > and i have already added localhost to xhost with the command: > xhost localhost > > but the error continue the same. > > r...@dejunliu-desktop:~# echo ${DISPLAY} > :0.0 >

Re: [Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-29 Thread Dejun.Liu
Hi, below is my DISPLAY info: echo ${DISPLAY} :0.0 and i have already added localhost to xhost with the command: xhost localhost but the error continue the same. r...@dejunliu-desktop:~# echo ${DISPLAY} :0.0 r...@dejunliu-desktop:~# xhost localhost localhost being added to access control list r

[Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-29 Thread Michael S. Tsirkin
No, I mean DISPLAY. On Sat, Dec 26, 2009 at 02:44:05PM -0300, Dejun.Liu wrote: > Hi, > > do u mean: > export SDL_VIDEODRIVER=x11 > ? > i hava set sdl video driver to x11. > > Steven Liu > > On Tue, 2009-12-29 at 12:04 +0200, Michael S. Tsirkin wrote: > > Most likely DISPLAY not set. > > > > O

[Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-29 Thread Dejun.Liu
Hi, do u mean: export SDL_VIDEODRIVER=x11 ? i hava set sdl video driver to x11. Steven Liu On Tue, 2009-12-29 at 12:04 +0200, Michael S. Tsirkin wrote: > Most likely DISPLAY not set. > > On Sat, Dec 26, 2009 at 07:40:01AM -0300, Dejun.Liu wrote: > > Hi, > > > > Im a newbie to qemu use. > > s

[Qemu-devel] Re: Help on "Could not initialize SDL - exiting"

2009-12-29 Thread Michael S. Tsirkin
Most likely DISPLAY not set. On Sat, Dec 26, 2009 at 07:40:01AM -0300, Dejun.Liu wrote: > Hi, > > Im a newbie to qemu use. > so i got a lot error!.. > > I build qemu from source with the version 0.10.3, > > But when i start qemu with the command below, i got the message > Could not in