[alsa-devel] ALSA versions versus kernel versions
tiwai at suse.de
Mon Jan 28 18:16:01 CET 2013
At Mon, 28 Jan 2013 12:06:34 -0500,
Daniel Griscom wrote:
> At 5:29 PM +0100 1/28/13, Takashi Iwai wrote:
> >At Mon, 28 Jan 2013 11:14:59 -0500,
> >Daniel Griscom wrote:
> > > But, I don't want to just install the alsa-driver-1.0.25 modules if
> >> more recent ones are included in the kernel distributions;
> >That's why I wrote you should forget alsa-driver packages.
> >> I only
> >> need whatever's in alsa-driver that is NOT in the kernel
> >> distributions, for example:
> >> - Is /etc/init.d/alsasound not needed? It seems to do a number of
> >> things on startup/shutdown.
> >It's a thing the distro should take care of. The installed one is a
> >reference init script. Forget this.
> >> - How can I independently install the ALSA headers: "make
> >> headers-install" inside alsa-driver-1.0.25?
> >The necessary header files are already included alsa-lib source tree,
> >and/or included in the kernel tree itself. You never need to install
> >them separately nowadays. Forget this.
> > > And, are there any other components that alsa-driver installs that
> >> are NOT included in the kernel distributions?
> >Basically nothing. Or, maybe alsa-info.sh. But this script can be
> >fetched from the web page as well.
> ... but how would I have known all this without grilling you?
Feel free to ask, and also update the information on alsa-project.org
web page. It's a Wiki, supposed to be updated by any users.
> "basically nothing" is a long way from "nothing" when you're dealing
> with an unfamiliar and poorly documented system.
Then how about start adding the new information you got now? :)
> > > >You seem to overestimate the numbers. I dream of dozen of core
> >> >developers, too.
> >> I hear you. But, that makes it even more important that the
> >> documentation be as complete as possible, so that a) you few
> >> developers don't get pestered by we not-yet-in-the-know users, and b)
> >> the knowledge you each have built up over the years isn't lost when
> >> one of you moves on to other projects.
> >Sure. But note that the information you've asked are all obsoleted
> >things. So, it won't be a big problem even if this information is
> >lost, unless anyone digging Trojan city again :)
> Not at all true: the fact that much of this is obsolete is itself undocumented.
> The alsa-project.org home page has a list of eight ALSA packages to
> download: there's no indication anywhere that any of them are
> considered obsolete. And the description of the various packages'
> contents is mostly missing; some of the packages include README files
> that describe contents, others have basically nothing (e.g. the
> description of the "alsa-tools" package is "Tools").
> I've registered for an alsa-project.org account, and I see that I
> could edit the Download page, but I'd likely get some of the details
> wrong. Five minutes by someone who did know the details, however,
> (e.g. you?) would greatly reduce your users' confusion.
Well, I don't know what user doesn't know. That's a part of the
problem. Documentation takes time, and replying this kind of mail
takes more time. So I'd really appreciate if anyone starts digging
into the web page, correct and update the information there. If
anything is missing or uncertain, feel free to ask on ML.
> My $0.02,
> >> >Speaking of implicit feedback: it's been since 3.5, but lots of bug
> >> >fixes are found in 3.7. So better to use 3.7, I guess.
> >> That's good information.
> >> >HTH,
> >> >
> >> >Takashi
> >> It most definitely does. Thank you.
> >> Dan
> >> P.S. And, I'll make sure to start a new thread next time.
> >> --
> >> Daniel T. Griscom griscom at suitable.com
> >> Suitable Systems http://www.suitable.com/
> >> 1 Centre Street, Suite 204 (781) 665-0053
> >> Wakefield, MA 01880-2400
> Daniel T. Griscom griscom at suitable.com
> Suitable Systems http://www.suitable.com/
> 1 Centre Street, Suite 204 (781) 665-0053
> Wakefield, MA 01880-2400
More information about the Alsa-devel