From: Michael Opdenacker <michael-lists@free-electrons.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: Jan Kiszka <jan.kiszka@googlemail.com>,
qemu-devel mailing list <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: How did you test sound on the Spitz emulation?
Date: Thu, 17 Jul 2008 11:58:58 +0200 [thread overview]
Message-ID: <487F17E2.3010807@free-electrons.com> (raw)
In-Reply-To: <fb249edb0807161552g41465089qdad23dac97c0850e@mail.gmail.com>
On 07/17/2008 12:52 AM, andrzej zaborowski wrote:
> 2008/7/16 Michael Opdenacker <michael-lists@free-electrons.com>:
>
>> How did you test the emulated WM8750 chip on the Spitz machine? Working
>> kernel configurations and qemu command line options are welcome!
>>
>
> I tested it with kernels and rootfs'es from pokylinux.org autobuilder,
> but they may have stopped working in the meantime. :(
> When I last tried to build a kernel for spitz outside OE, I had to
> apply ASoC patches from opensource.wolfsonmicro.com because ASoC was
> not in mainline yet (2.6.19 I think).
>
Thanks for your quick reply. That was a long time ago. I'll investigate
this in a few weeks as soon as I have enough time, and will try to fix
mainline Linux and/or qemu. I just wish I had access to the real
hardware...
>> Are there any other options to get both framebuffer and sound support
>> with qemu-system-arm?
>>
>
> Not any of those which have full Linux mainline support. Otherwise
> there is the PalmT|E (cheetah), MusicPal and Neo1973.
>
Thanks for the suggestions!
Cheers,
Michael.
--
Michael Opdenacker, Free Electrons
Kernel, drivers and embedded Linux development,
consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2008-07-17 9:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 21:13 [Qemu-devel] How did you test sound on the Spitz emulation? Michael Opdenacker
2008-07-16 22:52 ` [Qemu-devel] " andrzej zaborowski
2008-07-16 23:14 ` Jan Kiszka
2008-07-17 9:58 ` Michael Opdenacker [this message]
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=487F17E2.3010807@free-electrons.com \
--to=michael-lists@free-electrons.com \
--cc=balrogg@gmail.com \
--cc=jan.kiszka@googlemail.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).