From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Travis Place <wishie@wishie.net>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] Add some system information to alsa-info.sh output
Date: Tue, 1 Jul 2008 10:34:52 +0100 [thread overview]
Message-ID: <20080701093452.GA14666@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <1214847360.11032.9.camel@temp-fallen>
On Tue, Jul 01, 2008 at 03:36:00AM +1000, Travis Place wrote:
> On Mon, 2008-06-30 at 17:42 +0100, Mark Brown wrote:
> > How about bios_vendor, bios_date and bios_version as well?
> How useful is the BIOS information going to be, in most cases ?
Well, ideally most of the time all this information will be useless
since everything will work fine :) . I'd expect it to be useful
sometimes for handling things like broken information about setup for
HDA codecs.
> > For embedded devices the relevant information is often in /proc/cpuinfo
> > so it might be worth adding that too.
> Can i get an example output or 'cpuinfo' on an embedded device (if you
> have one available) so i can see what im looking for.
The particular output varies with platform and some platforms allow
machine drivers to add entirely custom fields - it's probably safest to
just include the entire file.
next prev parent reply other threads:[~2008-07-01 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 16:31 [PATCH] Add some system information to alsa-info.sh output Travis Place
2008-06-30 16:42 ` Mark Brown
2008-06-30 17:36 ` Travis Place
2008-07-01 9:34 ` Mark Brown [this message]
2008-07-01 9:50 ` Takashi Iwai
2008-07-01 9:52 ` Mark Brown
2008-07-01 9:48 ` 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=20080701093452.GA14666@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=wishie@wishie.net \
/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.