From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RFC][PATCH 4/4] Add support for Marvell 88w8618 / MusicPal
Date: Thu, 17 Apr 2008 21:06:14 +0200 [thread overview]
Message-ID: <48079FA6.3080104@web.de> (raw)
In-Reply-To: <fb249edb0804161724k41985897q46f71c8a0cc94de@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]
andrzej zaborowski wrote:
> Hi,
>
> On 13/04/2008, Jan Kiszka <jan.kiszka@web.de> wrote:
>> This is the board emulation for Freecom's MusicPal, featuring
>> - rudimentary PIT and PIC
>> - up to 2 UARTs
>> - 88W8xx8 Ethernet controller
>> - 88W8618 audio controller
>> - Wolfson WM8750 mixer chip (volume control and mute only)
>
> Are you sure that hw/wm8750.c is not reusable? It's probably better
> to extend it with volume control, and audio data transmission through
> i2c, instead of having two implementations in QEMU.
Will check again, but I don't think it is helpful, at least at this
point. The thing is that the MusicPal uses the on-chip DAC, not the one
of the Wolfson. The latter seems to be responsible for analogous mixing
only.
>
> Regarding volume control, since there are only 0x7f possible values
> it's nicer to use a const table than pull in math.h. Actually I
> wouldn't worry about that at all because the layout of volume levels
> on the host is not guaranteed to be linear (I think?), it may very
> well be already exponential. For example the Linux WM8750 driver
> doesn't do the reverse transformation which would mean that on a host
> whose ALSA output device is a WM8750, the Qemu vm would have a wrong
> volume scale.
[ Ignoring the above as advised in the follow-up, but will think about
avoiding or reducing the usage of pow(). ]
>
>> - 128×64 display with brightness control
>> - all input buttons
>>
>> Using up to 32 MB flash, I hit a limit /wrt phys_ram_size. I worked
>> around this for now by extending MAX_BIOS_SIZE to 32 MB, surely not a
>> nice solution.
>
> You can use -m 150 or similar.
>
> Please also format the code similarly to rest of Qemu.
That would just increase ram_size, thus won't help as I need memory
beyond it (here for the pflash in R/W mode).
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
next prev parent reply other threads:[~2008-04-17 19:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 10:11 [Qemu-devel] [RFC][PATCH 4/4] Add support for Marvell 88w8618 / MusicPal Jan Kiszka
2008-04-13 20:52 ` malc
2008-04-14 6:59 ` [Qemu-devel] " Jan Kiszka
2008-04-14 13:12 ` Stuart Brady
2008-04-14 16:21 ` Jan Kiszka
2008-04-14 16:49 ` malc
2008-04-14 17:47 ` Jan Kiszka
2008-04-15 17:38 ` malc
2008-04-15 21:03 ` Jan Kiszka
2008-04-16 18:40 ` malc
2008-04-17 19:06 ` Jan Kiszka
2008-04-14 19:21 ` Jan Kiszka
2008-04-14 21:34 ` Jan Kiszka
2008-04-17 0:24 ` [Qemu-devel] " andrzej zaborowski
2008-04-17 0:46 ` andrzej zaborowski
2008-04-17 19:06 ` Jan Kiszka [this message]
2008-04-18 18:12 ` [Qemu-devel] " Jan Kiszka
2008-04-18 18:43 ` andrzej zaborowski
2008-04-19 19:01 ` Jan Kiszka
2008-04-20 4:11 ` andrzej zaborowski
2008-04-20 15:52 ` Jan Kiszka
2008-04-20 17:38 ` andrzej zaborowski
2008-04-20 16:32 ` [Qemu-devel] [PATCH] " Jan Kiszka
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=48079FA6.3080104@web.de \
--to=jan.kiszka@web.de \
--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).