From: Wu Fengguang <fengguang.wu@intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [PATCH 1/4] alsa-info.sh: Do not automatically upload alsa info
Date: Wed, 8 Jul 2009 21:25:07 +0800 [thread overview]
Message-ID: <20090708132507.GA19706@localhost> (raw)
In-Reply-To: <20090708131503.905317376@intel.com>
On Wed, Jul 08, 2009 at 09:07:23PM +0800, Wu, Fengguang wrote:
> - the greeting dialog informs that the script collects info, waits
> for OK button. It affords a concrete listing of information to collect:
> /proc/asound/, aplay, etc. This not only shows respect for user privacy,
> but also serves as basic debugging tips for ALSA newbies.
> - when --upload option is given, the data will be automatically uploaded.
> - when --no-upload option is given, the data is just stored locally and quit.
> - when neither options are given, show a dialog to ask to upload or not.
>
> The above ideas mostly come from Takashi.
With this patch the dialogs will look like:
┌─────────────────────────ALSA-Info script v 0.4.56────────────────────────────┐
│ │
│ This script visits the following commands/files to collect diagnostic │
│ information about your ALSA installation and sound related hardware. │
│ │
│ lspci │
│ lsmod │
│ aplay │
│ amixer │
│ alsactl │
│ /proc/asound/ │
│ /sys/class/sound/ │
│ ~/.asoundrc (etc.) │
│ │
│ See './alsa-info.sh --help' for command line options. │
│ │
│ │
├──────────────────────────────────────────────────────────────────────────────┤
│ < OK > │
└──────────────────────────────────────────────────────────────────────────────┘
┌───────────────────────────Information collected──────────────────────────────┐
│ │
│ │
│ Automatically upload ALSA information to www.alsa-project.org? │
│ │
│ │
│ │
├──────────────────────────────────────────────────────────────────────────────┤
│ < UPLOAD / SHARE > < SAVE LOCALLY > │
└──────────────────────────────────────────────────────────────────────────────┘
┌─────────────────Information collected────────────────────┐
│ │
│ │
│ Your ALSA information is in /tmp/alsa-info.txt │
│ │
│ │
│ │
├──────────────────────────────────────────────────────────┤
│ < OK > │
└──────────────────────────────────────────────────────────┘
Thanks,
Fengguang
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2009-07-08 13:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 13:07 [PATCH 0/4] alsa-info.sh updates Wu Fengguang
2009-07-08 13:07 ` [PATCH 1/4] alsa-info.sh: Do not automatically upload alsa info Wu Fengguang
2009-07-08 13:25 ` Wu Fengguang [this message]
2009-07-08 13:07 ` [PATCH 2/4] alsa-info.sh: fix whitespace leaked to stdout Wu Fengguang
2009-07-08 13:07 ` [PATCH 3/4] alsa-info.sh: let mv fail loudly Wu Fengguang
2009-07-08 13:07 ` [PATCH 4/4] alsa-info.sh: introduce withall() Wu Fengguang
2009-07-09 16:51 ` [PATCH 0/4] alsa-info.sh updates Takashi Iwai
2009-07-09 17:03 ` Daniel Chen
2009-07-09 17:19 ` Mark Brown
2009-07-16 9:42 ` Takashi Iwai
2009-07-16 11:24 ` [PATCH] alsa-info.sh: add dmesg info on ALSA/HDA Wu Fengguang
2009-07-16 11:59 ` Takashi Iwai
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=20090708132507.GA19706@localhost \
--to=fengguang.wu@intel.com \
--cc=alsa-devel@alsa-project.org \
--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