Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Travis Place <wishie@wishie.net>
To: alsa-devel@alsa-project.org
Subject: Re: Ubuntu - Alsa Installation Script
Date: Fri, 31 Oct 2008 02:00:00 +1000	[thread overview]
Message-ID: <200810310200.00960.wishie@wishie.net> (raw)
In-Reply-To: <d9690f190810300103x31492740r9aa31830ea233f36@mail.gmail.com>

On Thursday 30 October 2008 6:03:55 pm Klaus Schulz wrote:
> Hi folks.
>
> I prepared an unofficial Alsa-Installation (now 1.0.18) script for the
> Ubuntu Community.
> The intention is mainly to be up2date on the drivers, since this - the lack
> or limited functionality
> of drivers (I am aware of the reasons behind it) is IMO still one of the
> biggest
> weaknesses within Linux. Therefore it is IMO crucial to have the latest
> driver available.
> As you know most of the distributions make things worse since these are
> usually one major release behind.
>
> http://ubuntuforums.org/showthread.php?t=962695
>
I will check this out, and see if i can make any suggestions.. also, you could 
specify a seperate dir to hold the NEW modules, and update the depmod search 
path (this is how i frequently tell ubuntu users to install alsa, from 
source).

> For standard installations the script seems to work fine.

We should be able to do a few tests, to determine things, and handle them 
differently etc.. If you've ever looked at the alsa-info.sh script, you'll 
know what i mean.. When originally writing that script, i wanted to take into 
account what 'interface' (if any) to use to display the output.. what 
information to collect (ac97/hda-intel) etc..

> Quite some people have been/are using it.
> And of course responding to it - mainly about problems on specific sound
> cards.
>
> I am wondering if things can be improved in the script. I would appreciate
> if
> somebody of the designers around here could have a quick look at it.

Im certainly no real expert, but it sounds like it would be a handy script, so 
worth a look into.

>
> I am not so deep into Alsa that I can cover severe problems brought up over
> there. How would you recommend to handle this?
>
> THX.
>
> Cheers
> Klaus
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

Thanks,
Travis Place (wishie)

  reply	other threads:[~2008-10-30 16:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30  8:03 Ubuntu - Alsa Installation Script Klaus Schulz
2008-10-30 16:00 ` Travis Place [this message]
2008-10-30 16:25   ` Klaus Schulz
2008-10-30 19:55     ` Mark Brown
2008-10-30 20:12       ` Daniel T Chen
2008-10-31 11:17         ` Mark Brown

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=200810310200.00960.wishie@wishie.net \
    --to=wishie@wishie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox