From: "Christian Rothländer" <Mailinglisten@rothlaender.net>
To: alsa-devel@alsa-project.org
Subject: Re: [PATCH] SM56 Modem in Asus A8J Notebook Series
Date: Fri, 18 May 2007 16:45:40 +0200 [thread overview]
Message-ID: <464DBC14.3080308@rothlaender.net> (raw)
In-Reply-To: <s5hmz02mce9.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 1695 bytes --]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> > It's a process to merge to the upstream kernel. We need to give a
> > kind of approval from the patch authors and contributors.
> > It consists of a line
ok .. something new for me :-)
Here it goes:
Signed-off-by: Christian Rothlaender <christian@rothlaender.net>
================================================================
hda-codec - patch_si3045.c
This patch adds support for the ASUS A8J Series 56k Modem (Motorola SM56)
Signed-off-by: Christian Rothlaender <christian@rothlaender.net>
THE PATCH STARTS BELOW
================================================================
> Just a small issue is left. With the alsa driver buildin into 2.6.19
> slmodem is working, with any newer one (either
> standalone or buildin driver) we have a "hda-intel: invalid
> format_val, rate=9600, ch=1, format=2" error in dmesg. Seems
> something has been broken on that step (probably 1.0.13 to
> 1.0.14?). Sadly I'm not able to tell right now which alsa was
> included into 2.6.19. I'm trying to compare the files to get an idea
> what's wrong (#2799 and #2820 are reporting similar
> problems).
> >
> > This should have been fixed in the recent version.
> > The driver dropped the support of 9600HZ accidentally.
That's really good to hear. Can you close the Bug entry #2732 then?
(#2799 and #2820 can be closed too, if the 9600 Hz problem is solved)
So thanks a lot ...
Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGTbwUYMBp7Qf+VpkRApyKAJ4xfBkrLiG1D7whZIV1CteUTRhFagCfd/LU
2jeMsy1MQ/WxX5A7P/iThjM=
=A9s6
-----END PGP SIGNATURE-----
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3839 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2007-05-18 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 13:17 [PATCH] SM56 Modem in Asus A8J Notebook Series Christian Rothländer
2007-05-18 14:10 ` Takashi Iwai
[not found] ` <464DB5E8.202@rothlaender.net>
[not found] ` <s5hmz02mce9.wl%tiwai@suse.de>
2007-05-18 14:45 ` Christian Rothländer [this message]
2007-05-18 14:59 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 14:22 Christian Rothländer
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=464DBC14.3080308@rothlaender.net \
--to=mailinglisten@rothlaender.net \
--cc=alsa-devel@alsa-project.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.