From: Igor Kovalenko <garrison@mail.ru>
To: Raymond <rayau@netvigator.com>
Cc: alsa-devel@lists.sourceforge.net, openvortex-dev@nongnu.org
Subject: Re: [Openvortex-dev] Re: Re: [ALSA - driver 0001138]: errors when installing au8820 modules
Date: Wed, 08 Jun 2005 22:03:49 +0400 [thread overview]
Message-ID: <42A73305.9000000@mail.ru> (raw)
In-Reply-To: <42A6E5BE.4030003@netvigator.com>
Raymond wrote:
> Is there any way to remove this warning for the change from "0x%08lx" to
> "0x%08x" in 32-bits compiler ?
>
> warning: unsigned int format, long unsigned int arg (arg 2)
>
> There is no warning before this change.
>
>
> alsa-kernel/pci/au88x0/au88x0_core.c
>
> @@ -1054,7 +1054,7 @@
> hwwrite(vortex->mmio, addr, FIFO_U0);
> if (hwread(vortex->mmio, addr) != FIFO_U0)
> printk(KERN_ERR
> - "bad wt fifo reset (0x%08lx, 0x%08x)!\n",
> + "bad wt fifo reset (0x%08x, 0x%08x)!\n",
> addr, hwread(vortex->mmio, addr));
> vortex_fifo_clearwtdata(vortex, x, FIFO_SIZE);
> addr -= 4;
>
>
>>
>> Well, I've not stated the problem clearly enough.
>> Once set, volume stays as it should. The problem is that
>> PCM volume is:
>> 1% - at lowest audible level
>> 25% - at about 50% audible level
>> 49% - at about max audible level
>> 51% - at lowest audible level
>> 75% - at about 50% audible level
>> 99% - at about max audible level
>> - that is what I described as low-high-low-high.
>> On the other hand, Master volume behaves as expected.
>
>
>
> What is the value of comment.range of 'PCM Playback Volume' in
> /etc/asound.state for your STAC9704 (au8820) ?
>
>
> According to 9704SPEC.pdf, it should be '0-31' ( 5 bits ) for STAC9704
> PCM Out volume.
>
control.21 {
comment.access 'read write'
comment.type INTEGER
comment.count 2
comment.range '0 - 63'
iface MIXER
name 'PCM Playback Volume'
value.0 21
value.1 21
}
Do you mean AC97 is incorrectly reporting 0...63 range?
> or check the values *low_max and *high_max return by
> check_volume_resolution()
>
> http://cvs.sourceforge.net/viewcvs.py/alsa/alsa-kernel/pci/ac97/ac97_codec.c?r1=1.163&r2=1.164
>
>
>
> Igor Kovalenko wrote:
>
>> Takashi Iwai wrote:
>>
>>> At Tue, 7 Jun 2005 17:16:02 +0200,
>>> Alien wrote:
>>>
>>>
>>>> [1 <text/plain; iso-8859-1 (quoted-printable)>]
>>>> Op dinsdag 7 juni 2005 17:05, schreef Raymond:
>>>>
>>>>
>>>>> The patch (diff11.diff) cause segmenation fault on my 32bit machine
>>>>> during /etc/init.d/alsasound start
>>>>>
>>>>> http://savannah.nongnu.org/patch/?func=detailitem&item_id=3948
>>>>>
>>>>> Do anyone know why readl() and writel() behave different in i386
>>>>> (32bits) and AMD64 (64bits) ?
>>>>>
>>>>> http://sourceforge.net/mailarchive/message.php?msg_id=10773530
>>>>>
>>>>>
>>>>> #ifndef CONFIG_X86_64
>>>>>
>>>>> #define hwread(x,y) readl((x)+((y)>>2))
>>>>> #define hwwrite(x,y,z) writel((z),(x)+((y)>>2))
>>>>>
>>>>> #else
>>>>>
>>>>> #define hwread(x,y) readl((x)+(y))
>>>>> #define hwwrite(x,y,z) writel((z),(x)+(y))
>>>>>
>>>>> #endif
>>>>
>>>>
>>>> that doesn't look good, unless the mmio is void* in 32bit and
>>>> unsigned long* in x86_64...
>>>>
>>>> 'unsigned long* mmio' should be preferred and together with
>>>> '#define hwread(x,y) readl((x)+(y))' , this works for both
>>>> platforms
>>>
>>>
>>>
>>> I guess using "unsigned long" for both architectures is broken, too.
>>> Should be "u32" to be arch-independent.
>>>
>>
>>
>> I strongly believe readl() and writel() on x86_64 does 32 bit
>> reads/writes.
>> (checked linux-2.6.12-rc5). Therefore reads/writes are of correct size
>> with
>> that patch - should be something different.
>>
>
>
>
>
>
> _______________________________________________
> Openvortex-dev mailing list
> Openvortex-dev@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/openvortex-dev
>
>
--
Kind regards,
Igor V. Kovalenko
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
next prev parent reply other threads:[~2005-06-08 18:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-28 20:22 [ALSA - driver 0001138]: errors when installing au8820 modules bugtrack
2005-06-06 2:09 ` Raymond
2005-06-06 15:49 ` Takashi Iwai
2005-06-07 15:05 ` Raymond
2005-06-07 15:16 ` Alien
2005-06-07 16:29 ` Takashi Iwai
2005-06-07 17:05 ` [Openvortex-dev] " Igor Kovalenko
2005-06-07 17:17 ` Alien
2005-06-07 17:38 ` Igor Kovalenko
2005-06-07 18:02 ` Alien
2005-06-08 10:18 ` Takashi Iwai
2005-06-08 11:13 ` Alien
2005-06-08 12:12 ` Takashi Iwai
2005-06-08 13:29 ` Alien
2005-06-08 13:41 ` Takashi Iwai
2005-06-08 18:09 ` Igor Kovalenko
2005-06-08 11:40 ` Raymond
2005-06-08 12:19 ` Takashi Iwai
2005-06-08 18:12 ` Igor Kovalenko
2005-06-09 8:13 ` Raymond
2005-06-08 12:34 ` Raymond
2005-06-08 12:43 ` Takashi Iwai
2005-06-08 18:03 ` Igor Kovalenko [this message]
2005-06-09 8:54 ` Raymond
2005-06-28 7:50 ` Raymond
2005-07-01 19:03 ` Igor Kovalenko
2005-07-02 12:53 ` Raymond
2005-07-14 16:43 ` Igor Kovalenko
2005-06-08 9:06 ` Raymond
2005-06-08 10:22 ` Takashi Iwai
2005-06-09 8:34 ` Raymond
2005-06-09 10:17 ` [Openvortex-dev] " Igor Kovalenko
2005-06-12 15:18 ` Raymond
2005-06-10 7:35 ` Raymond
2005-06-10 10:33 ` Takashi Iwai
2005-06-10 11:28 ` Raymond
2005-07-29 14:43 ` Raymond
2005-07-29 15:09 ` Takashi Iwai
2005-08-05 12:46 ` Raymond
2005-08-05 14:32 ` Takashi Iwai
[not found] ` <43067D3B.5040601@netvigator.com>
2005-08-21 12:41 ` Takashi Iwai
2005-08-23 15:20 ` Raymond
2005-08-23 17:18 ` Takashi Iwai
2005-08-23 21:40 ` Alien
2005-08-24 10:35 ` Takashi Iwai
2005-08-25 17:12 ` Raymond
2005-08-25 17:43 ` Alien
2005-08-26 9:01 ` Raymond
2005-08-25 18:58 ` Manuel Jander
2005-08-25 20:04 ` Alien
2005-06-08 10:23 ` Alien
2005-06-09 8:49 ` Raymond
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=42A73305.9000000@mail.ru \
--to=garrison@mail.ru \
--cc=alsa-devel@lists.sourceforge.net \
--cc=openvortex-dev@nongnu.org \
--cc=rayau@netvigator.com \
/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