Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rimas Kudelis <rq@akl.lt>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel HDA and Realtek ALC 260
Date: Mon, 06 Feb 2006 07:42:09 +0200	[thread overview]
Message-ID: <43E6E1B1.3000405@akl.lt> (raw)
In-Reply-To: <200602060229.k162THBb025229@auster.physics.adelaide.edu.au>

[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]

Hello Jonathan,

>>I'm one of the people affected by
>>https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1618. ... So I have
>>a question for the maintainer of that module (I guess that's jwoithe)
>>    
>>
>Not to my knowledge - I've just provided the Fujitsu model and some other
>more general patches to patch-realtek.c because I have a laptop with the
>ALC260 in it and want it to work. :) Takashi would be the official
>maintainer of this file AFAIK.
>  
>
Ah, I see.

>>would it be possible to add a "test" model, like in case of ALC880, which
>>would have controls for all of the chipset pins available? I guess that
>>would simplify things a lot...
>>    
>>
>I think that's possibly worth considering.  I'll have a look into this
>tonight and see how much extra code it would add.  Since most of the
>infrastructure is already present I suspect it won't be too bad.  Such a
>feature would allow people to test new computers without having to patch
>anything and as such would probably be quite useful, as you suggest.
>

Thank you. Also, it would be useful for this model to add mixer controls
for retasking pins, as you did with Fujitsu model. That would hopefully
allow to quickly test what pins are connected to what jacks/hardware
(i.e., one could connect external speakers/headphones to all sound jacks
first). And the naming of controls - I suppose these should either be
named the way Paulo has named them (0x08 Volume, for example), or
similar to what they are marked in Realtek datasheet. That would make
things even easier for you developers to add new models based on user input.

BTW the notebook i'm having this problem with is an Acer Travelmate 4060
series, like Paulo's (but 4061 in my case), so I could help you
test/debug the Acer model specifics. Don't hesitate to contact me
regarding this.

Hope to hear from you soon.

Rimas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2006-02-06  5:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06  2:29 Intel HDA and Realtek ALC 260 Jonathan Woithe
2006-02-06  5:42 ` Rimas Kudelis [this message]
2006-02-06 23:04   ` Jonathan Woithe
  -- strict thread matches above, loose matches on Subject: below --
2006-02-04 10:17 Rimas Kudelis

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=43E6E1B1.3000405@akl.lt \
    --to=rq@akl.lt \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    /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