alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org,
	"Manolo Díaz" <diaz.manolo@gmail.com>,
	"Miro Hodak" <mhodak127@gmail.com>,
	basinilya@gmail.com,
	"David Henningsson" <david.henningsson@canonical.com>
Subject: Re: hda_analyzer failed
Date: Wed, 6 Feb 2013 16:10:56 +0800	[thread overview]
Message-ID: <CAN8cciaR6dLJpTURvw67RT1psU9qgz28_-YAtyVwdrHr6gtFMQ@mail.gmail.com> (raw)
In-Reply-To: <s5h38x97we1.wl%tiwai@suse.de>

2013-2-6 下午3:07 於 "Takashi Iwai" <tiwai@suse.de> 寫道:
>
> At Wed, 6 Feb 2013 13:35:37 +0800,
> Raymond Yau wrote:
> >
> > [1  <text/plain; UTF-8 (7bit)>]
> > >>
> > >>  > File "/dev/shm/hda-analyzer/hda_proc.py", line 143, in wrongfile
> > >>  >     raise ValueError, "wrong proc file format (%s)" % msg
> > >>  > ValueError: wrong proc file format (integer decode 'State of AFG
node
> > >> 0x01:' ('Node '))
> > >>  >
> > >>  > Any ideas?
> > >>
> > >> This patch add lines which make the parser of hda_proc.py fail
> > >>
> > >>
> >
http://git.kernel.org/?p=linux/kernel/git/tiwai/sound.git;a=commitdiff;h=f4f0a8c4783a0258f2d0020a67fd619ce41a02a3;hp=e4cc6153401fc59d6d4ca0317be5774bdbd399ba
> > >>
> > >
> > > Sigh, this is not the first time new stuff in the proc file crashes
> > hda_analyzer.
> > >
> > > Jaroslav, can you please fix hda_analyzer so that it ignores new
stuff in
> > the proc file instead of crashing, so we don't have this problem over
and
> > over again?
> > >
> >
> > I don`t understand why the parser have to ignore new stuff
>
> Because usually such a new entry is no critical item but extra
> information.  Of course, hda_analyzer can warn such entries.  But it's
> totally different from aborting as a fatal error.
>
> > BTW, why hda_proc query the connection list of vendor defined widget ?
> >
> >
http://git.kernel.org/?p=linux/kernel/git/tiwai/hda-emu.git;a=blob;f=codecs/ad1882-sparta;hb=HEAD
> >
> > Node 0x23 [Vendor Defined Widget] wcaps 0xf00100: Mono
> >    Connection: -22
>
> Unrelated topic.
>

Ad1988 also has this ( VREF Power-Down) Vendor defined Powers down the
internal and external VREF circuitry

If is confusing that 0x11 is displayed as selected

Node 0x23 [Vendor Defined Widget] wcaps 0xf00100: Mono
  Connection: 18
     0x11* 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x24 0x25 0x38 0x39 0x3a
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2013-02-06  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN8cciaewnb1f9G7nhE+06GBZiUgJvZ5LwTz+AFmLcHJoYjzhw@mail.gmail.com>
     [not found] ` <CAN8cciZqkGH5mK_vn20m023YYgc3UC7okBXHobmdj3Tqibamiw@mail.gmail.com>
2013-02-06  5:35   ` hda_analyzer failed Raymond Yau
2013-02-06  7:07     ` Takashi Iwai
2013-02-06  8:10       ` Raymond Yau [this message]
2013-02-06 12:38     ` Manolo Díaz

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=CAN8cciaR6dLJpTURvw67RT1psU9qgz28_-YAtyVwdrHr6gtFMQ@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=basinilya@gmail.com \
    --cc=david.henningsson@canonical.com \
    --cc=diaz.manolo@gmail.com \
    --cc=mhodak127@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;
as well as URLs for NNTP newsgroup(s).