From: Takashi Iwai <tiwai@suse.de>
To: Ricardo Cerqueira <alsa-users@cerqueira.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: (Was Re: [Alsa-user] Poorly supported HDA intel)
Date: Fri, 20 Oct 2006 18:48:13 +0200 [thread overview]
Message-ID: <s5hpscn0w8i.wl%tiwai@suse.de> (raw)
In-Reply-To: <d8b81e372610a33f6719ca6000ce830f@192.168.1.254>
At Fri, 20 Oct 2006 18:35:43 +0200,
Ricardo Cerqueira wrote:
>
>
>
> On Fri, 20 Oct 2006 18:18:09 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> > At Fri, 20 Oct 2006 17:55:23 +0200,
> > Ricardo Cerqueira wrote:
> >>
> >> On Fri, 20 Oct 2006 17:52:56 +0200, Takashi Iwai <tiwai@suse.de> wrote:
> >> > At Fri, 20 Oct 2006 17:48:00 +0200,
> >>
> >> >>
> >> >> Hmmm. I was trying to look into codec#0 to check the pin assignments,
> >> > and I
> >> >> realized it's being cut off at byte 4096, and I'm missing
> > information.
> >> > Looks
> >> >> like something is limiting that proc entry's size to 4k, do you have
> > any
> >> > idea
> >> >> where?
> >> >
> >> > Are your using HG version of driver?
> >> > This bug should have been fixed recently.
> >> >
> >> >
> >>
> >> Yes, pulled about 14 hours ago...
> >
> > Strange, it works for me. I tested to print extra data up to 32k
> > bytes on my i386 machine, and it looks OK.
> >
> > Check alsa-kernel hg tree whether you have a changeset 4658
> > "Fix re-use of va_list" (although it should work even without this
> > patch on i386).
>
> Yes, I'm at changeset 4662... I checked core/info.c by hand, and the va_list
> change is there... I just tried cloning fresh copies of alsa-kernel and
> alsa-driver, and the result is the same.
Weird. Could you check whether really it's 4k boundary problem?
For example, try the patch below to see whether you get 500 dummy
lines in codec#0 proc file.
Takashi
diff -r d7fe584f7395 pci/hda/hda_proc.c
--- a/pci/hda/hda_proc.c Thu Oct 19 20:35:56 2006 +0200
+++ b/pci/hda/hda_proc.c Fri Oct 20 18:42:07 2006 +0200
@@ -202,6 +202,9 @@ static void print_codec_info(struct snd_
hda_nid_t nid;
int i, nodes;
+ for (i = 0; i < 500; i++)
+ snd_iprintf(buffer, "[%d] XXXXX DUMMY LINE XXXX XXXX DUMMY LINE XXXX\n", i);
+
snd_hda_get_codec_name(codec, buf, sizeof(buf));
snd_iprintf(buffer, "Codec: %s\n", buf);
snd_iprintf(buffer, "Address: %d\n", codec->addr);
-------------------------------------------------------------------------
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-10-20 16:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5h64ef2gu3.wl%tiwai@suse.de>
[not found] ` <d216214ec4416bdd3239c871772e9cc4@192.168.1.254>
2006-10-20 15:14 ` [Alsa-user] Poorly supported HDA intel Takashi Iwai
2006-10-20 15:24 ` Ricardo Cerqueira
2006-10-20 15:48 ` Ricardo Cerqueira
2006-10-20 15:52 ` Takashi Iwai
2006-10-20 15:55 ` Ricardo Cerqueira
2006-10-20 16:18 ` Takashi Iwai
2006-10-20 16:35 ` Ricardo Cerqueira
2006-10-20 16:48 ` Takashi Iwai [this message]
2006-10-20 16:55 ` (Was Re: [Alsa-user] Poorly supported HDA intel) Ricardo Cerqueira
2006-10-20 17:16 ` Ricardo Cerqueira
2006-10-23 11:12 ` Takashi Iwai
2006-10-23 11:36 ` Takashi Iwai
2006-10-29 11:45 ` Ricardo Cerqueira
2006-10-24 19:08 ` (no subject) Thierry Vignaud
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=s5hpscn0w8i.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-users@cerqueira.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.