From: Kailang <kailang@realtek.com>
To: "Aurélien Croc" <aurelien@ap2c.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>
Subject: RE: [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy book
Date: Mon, 2 Mar 2020 07:00:18 +0000 [thread overview]
Message-ID: <672a747738f348d78bd47d044a2b8368@realtek.com> (raw)
In-Reply-To: <3045783.YgvgG0t98J@antimony.ap2c.org>
> -----Original Message-----
> From: Aurélien Croc <aurelien@ap2c.com>
> Sent: Saturday, February 29, 2020 1:40 AM
> To: alsa-devel@alsa-project.org
> Cc: Kailang <kailang@realtek.com>; Takashi Iwai <tiwai@suse.de>
> Subject: Re: [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy
> book
>
> > Sorry.
> > Samsung didn't request this platform need to support Linux.
>
> I can understand that you can't work on my problem if your client (Samsung)
> didn't paid for that. However is it possible to get ALC298 specs in order to
> understand how-to configure it (in particular a document which explains its
> COEF registers and their meaning) and I will do the job.
>
Hi,
OK. I could try to request spec from our AE.
> Thank you in advance.
> Regards,
>
> Aurélien
>
>
>
> ------Please consider the environment before printing this e-mail.
next prev parent reply other threads:[~2020-03-02 7:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-15 16:56 [alsa-devel] No sound with Realtek ALC298 on a Samsung Galaxy book Aurélien Croc
2020-02-17 8:00 ` Takashi Iwai
2020-02-17 14:03 ` Aurélien Croc
2020-02-17 16:19 ` Takashi Iwai
2020-02-17 19:01 ` Aurélien Croc
2020-02-17 22:05 ` Takashi Iwai
2020-02-19 8:48 ` Kailang
2020-02-29 12:37 ` Aurélien Croc
[not found] ` <3045783.YgvgG0t98J@antimony.ap2c.org>
2020-03-02 7:00 ` Kailang [this message]
2020-02-19 9:05 ` Aurélien Croc
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=672a747738f348d78bd47d044a2b8368@realtek.com \
--to=kailang@realtek.com \
--cc=alsa-devel@alsa-project.org \
--cc=aurelien@ap2c.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