From: Tobin Davis <tdavis@dsl-only.net>
To: "Daniele (Mastro)" <daniele.bilug@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: Notebook Toshiba satellite x200-21g with realtek snd-hda-intel audio device still not supported (codec ALC268)
Date: Thu, 27 Dec 2007 20:15:21 -0800 [thread overview]
Message-ID: <1198815321.3732.229.camel@razman.gruemaster.com> (raw)
In-Reply-To: <47727C6C.6080401@gmail.com>
Ok, I'm going to dive into this one this weekend. I have a test board
ready to run.
Daniele, please email me off list to keep the noise level down. I'm
also tracking this in bugzilla.
Tobin
On Wed, 2007-12-26 at 17:08 +0100, Daniele (Mastro) wrote:
> Takashi Iwai ha scritto:
> > I recommend you to hack the driver code by yourself.
> > The coding itself isn't too difficult. The problem is the guess work,
> > which PIN really corresponds to which I/O, and what control is missing
> > (EAPD, GPIO, etc).
>
> hum..
> i guess the file i should edit is patch_realtek.c
> but i really have no idea on what to change/add and how to understand
> what i have to change...
>
> in my other message there are the debug info you requested and i don't
> know how to use them
>
> i'm really want to do something to help you but i keep reading the code
> without knowing what to do or understanding it very much... i never
> developed kernel drivers and I've no idea on what to do
>
> I'm putting here my good will but think i miss the knowledge to do what
> you suggested and i don't know where to achieve it either
>
> > What I'm wondering is how to support 5.1 output. The ALC268 codec is
> > at most for 4 channels (2 + 2). Are you sure that you can get 5.1
> > distinct outputs?
>
> probably this isn't a 5.1 as i said in the other message
>
> thanks for any reply you will give me
> i'm sorry i'm so annoying
>
next prev parent reply other threads:[~2007-12-28 4:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 2:09 Notebook Toshiba satellite x200-21g with realtek snd-hda-intel audio device still not supported (codec ALC268) Daniele (Mastro)
2007-12-19 12:47 ` Daniele (Mastro)
2007-12-20 8:46 ` Daniele (Mastro)
2007-12-20 14:03 ` Takashi Iwai
2007-12-21 0:04 ` Daniele (Mastro)
2007-12-21 1:10 ` Tobin Davis
2007-12-21 10:14 ` Daniele (Mastro)
2007-12-24 20:40 ` Daniele (Mastro)
2007-12-26 16:08 ` Daniele (Mastro)
2007-12-26 21:13 ` Tobin Davis
2007-12-28 4:15 ` Tobin Davis [this message]
2008-02-11 15:46 ` Daniele (Mastro)
2008-02-11 16:09 ` Takashi Iwai
2008-02-11 16:31 ` Takashi Iwai
2008-02-11 22:58 ` Daniele (Mastro)
2008-02-12 10:23 ` Takashi Iwai
2008-02-13 0:32 ` Daniele (Mastro)
2008-02-15 17:56 ` Daniele (Mastro)
2008-02-18 18:06 ` Daniele (Mastro)
2008-02-19 14:02 ` Takashi Iwai
2008-02-19 14:18 ` Daniele (Mastro)
2008-02-19 14:34 ` Takashi Iwai
2008-02-19 15:03 ` Daniele (Mastro)
2008-02-19 15:10 ` Takashi Iwai
2008-02-19 15:55 ` Daniele (Mastro)
2008-02-19 16:15 ` Takashi Iwai
2008-02-19 17:29 ` Daniele (Mastro)
2008-02-19 18:16 ` Tobin Davis
2008-02-19 18:52 ` Daniele (Mastro)
2008-02-19 19:01 ` Tobin Davis
-- strict thread matches above, loose matches on Subject: below --
2007-12-16 14:35 Daniele (Mastro)
2007-12-17 10:03 ` Takashi Iwai
2007-12-17 14:13 ` Daniele (Mastro)
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=1198815321.3732.229.camel@razman.gruemaster.com \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=daniele.bilug@gmail.com \
--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