public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Flater <vger@flaterco.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Jaroslav Kysela <perex@perex.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	Alsa Devel <alsa-devel@alsa-project.org>
Subject: Re: [PATCHv2 1/2] ALSA: fix emu8000 DRAM sizing for AWE64 Value
Date: Sun, 11 Jan 2015 12:10:06 -0500	[thread overview]
Message-ID: <54B2AE6E.3080909@flaterco.com> (raw)
In-Reply-To: <s5h7fwt4mji.wl-tiwai@suse.de>

On 01/11/2015 05:52 AM, Takashi Iwai wrote:
> At Fri, 09 Jan 2015 19:50:36 -0500,
> David Flater wrote:
>> CT4380 is commonly said to come with 1 MiB of DRAM, but Creative's AWE
>> Control app agreed that mine has only 512 KiB.  It has the same memory chip
>> as the CT4520.
> 
> And you couldn't actually use the 1MB, right?

Confirmed with indirect evidence.  Since the address space wraps around, the mode of failure (assuming that the load isn't blocked by checking against a correctly detected size) is silent corruption of the loaded sound font.

Testing with a random sound font larger than 512 KiB but smaller than 1 MiB:
Fender2.sf2, 545994 B

On CT4390, the following test gives me a credible guitar in the left channel (and nothing else):
asfxload -i -M Fender2.sf2
DRAM memory left = 3565 kB
aplaymidi -p 17:0 E1M1.mid

On CT4380 with DRAM size hard-coded to 1 MiB, asfxload catches no failure but aplaymidi produces a glitchy mixture of guitar and morse code beeping:
asfxload -i -M Fender2.sf2
DRAM memory left = 493 kB
aplaymidi -p 17:0 E1M1.mid

DWF


      reply	other threads:[~2015-01-11 17:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10  0:50 [PATCHv2 1/2] ALSA: fix emu8000 DRAM sizing for AWE64 Value David Flater
2015-01-11 10:52 ` Takashi Iwai
2015-01-11 17:10   ` David Flater [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=54B2AE6E.3080909@flaterco.com \
    --to=vger@flaterco.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.de \
    /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