From: Matthias Lemke <m@box.li>
To: alsa-devel@lists.sourceforge.net
Cc: Takashi Iwai <tiwai@suse.de>
Subject: Re: problem with alsa on Sony UX-90s
Date: Mon, 13 Nov 2006 13:47:59 +0100 [thread overview]
Message-ID: <4558697F.3000004@box.li> (raw)
In-Reply-To: <s5hveljbnit.wl%tiwai@suse.de>
Takashi Iwai schrieb:
> At Sat, 11 Nov 2006 14:30:45 +0100,
> Matthias Lemke wrote:
>>>>> If none of the existing model matches with yours, we'd need to create
>>>>> a new model. Load the driver without model option, and show the
>>>>> content of /proc/asound/card0/codec#* file. If we have luck, the BIOS
>>>>> sets up a speaker pin...
>>>> I added this output to my bug:
>>>> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2605
>>> Please post it to here, too. (Honestly I hate debugging on BTS with a
>>> bad interface :)
>> ok, some models working!
>> for instance basic, hippo.
>> I assume I have a mono speaker. So every model with a "mono" channel
>> works. Auto has no Mono channel.
>> Also the internal Mic works. I cant check line in at the moment...
>> auto doesnt work correctly.
>
> The difference between basic and hippo models is that hippo supports
> the HP-jack detection and mutes the speaker automatically. Does the
> auto-mute work on your machine?
what do You mean?
with hippo and with basic i have the following behaviour:
- speaker switches off while inserting headphones
- alsamixer shows no muting automatically while inserting
should I check some other things?
>
> Also hippo adds the digital output support, but it would be harmless
> anyway even if the device has no SPDIF output.
ok, no SPDIF here...
>
>> should we do some´additions in the code for autoconfig?
>
> If the auto-mute is working and there is no obvious missing function,
> we can add the entry for your device to the driver code so that
> model=hippo will be chosen automatically in future. Then let me know
> the output of "lspci -nv" (only for class 0403 entry) to add the
> corresponding PCI SSID.
00:1b.0 0403: 8086:27d8 (rev 02)
Subsystem: 104d:8203
Flags: bus master, fast devsel, latency 0, IRQ 66
Memory at d4340000 (64-bit, non-prefetchable) [size=16K]
Capabilities: [50] Power Management version 2
Capabilities: [60] Message Signalled Interrupts: 64bit+
Queue=0/0 Enable+
Capabilities: [70] Express Unknown type IRQ 0
Capabilities: [100] Virtual Channel
Capabilities: [130] Unknown (5)
regards
math
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next prev parent reply other threads:[~2006-11-13 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 15:28 problem with alsa on Sony UX-90s Matthias Lemke
2006-11-10 11:36 ` Takashi Iwai
2006-11-10 12:19 ` Matthias Lemke
2006-11-10 13:22 ` Takashi Iwai
2006-11-11 13:30 ` Matthias Lemke
2006-11-13 11:21 ` Takashi Iwai
2006-11-13 12:47 ` Matthias Lemke [this message]
2006-11-13 13:26 ` Takashi Iwai
2006-11-14 11:20 ` Matthias Lemke
2006-11-14 11:31 ` Takashi Iwai
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=4558697F.3000004@box.li \
--to=m@box.li \
--cc=alsa-devel@lists.sourceforge.net \
--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