All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Vignaud <tvignaud@mandrakesoft.com>
To: Paul Davis <pbd@op.net>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@lists.sourceforge.net
Subject: Re: questions for alsa-devel
Date: Wed, 02 Oct 2002 16:07:42 +0200	[thread overview]
Message-ID: <m27kh1djdd.fsf@vador.mandrakesoft.com> (raw)
In-Reply-To: <200210021357.g92DvYsu010195@smtp.mandrakesoft.com> (Paul Davis's message of "Wed, 02 Oct 2002 09:58:34 -0400")

Paul Davis <pbd@op.net> writes:

> > hum, mdk9.0 is compiled with module versionning and we've no
> > problems (i mean there're bugs but not such problems)
>
> this is 8.2 ...

this means that we compile rc3 with versionning symbols without
problems, so this answer takashi fear

> i have a bit of a problem with all of this. why doesn't ALSA build
> "out of the box"? the description you've given of what is necessary
> to get this to work seems (for the most part) to be a bit
> ridiculous.

insulting people that take time to answer you has always been a
constructive & efficient communication way.

> > 4) note that if you boot with a kernel with alsa-0.9.0, all your
> >    alsa apps won't work unless you use them in oss emulation mode.
>
> why is this? note that i never compile ALSA as part of the kernel,
> and i doubt that i ever will, even when 2.5/2.6/3.0 comes out. i
> prefer to be able to update my drivers without touching my kernel
> source.

the problem will remains the same whatever you compiled the alsa
modules in the same time you compiled the kernel or as a separate
pacakge : applications linked with alsa-0.5 library won't be able to
dialog with alsa-0.9.0 kernel ...

> updating from 8.2 to 9.0 over a 56k link strikes me as a pretty
> absurd step to take.

then, unless you absolutely need the fixes provided by the latest alsa
driver for your card, there's no point in upgrading it without
upgrading libalsa and relevant applications...

> having to specifically install kernel source to compile ALSA (and
> presumably other drivers) seems very odd to me. i would understand
> if ALSA just failed to compile without that step, but i didn't ask
> for or say no to a kernel source package, and ALSA compiled just
> fine.

alsa can compile fine as an extra package providing you've kernel
headers and the right links in /boot and /lib/modules (config, build,
System.map, ...)

> frankly, i was very suprised to get ALSA 0.5 in mdk8.2. its been
> publically stated for months and months that 0.5 is no longer under
> development and is not really supported (though takashi has done a
> great job with it). i did a quick search with rpmdrake to see if a
> 0.9.0 rpm was on the installation disks, but i couldn't find it.

mdk8.2 is more than 6 monthes old; i don't have yet time support in
tcp/ip to download future version of alsa-0.9.0 when only stable
versions of alsa-0.5.x were out...

the point of alsa-0.5.x integration in mandrake kernel was more
drivers (there're lots of cards not supported by oss drivers but by
alsa. eg the fm801 i used to have)

we also put the corresponding alsa libs and tools since they enable
some more features in some apps.

if you want less drivers and less features, that's your problem.



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

       reply	other threads:[~2002-10-02 14:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200210021357.g92DvYsu010195@smtp.mandrakesoft.com>
2002-10-02 14:07 ` Thierry Vignaud [this message]
     [not found]   ` <20021002145420.6F590146FB@Cantor.suse.de>
2002-10-02 15:03     ` Forward: Re: questions for alsa-devel Takashi Iwai
2002-10-02 15:25       ` Takashi Iwai
2002-10-02 15:43         ` Matthias Saou
2002-10-02 17:19           ` Thierry Vignaud
2002-10-02 17:25             ` Matthias Saou
2002-10-02 18:01               ` Jack O'Quin
2002-10-02 18:26               ` Thierry Vignaud
2002-10-02 21:49             ` Audiophile 2496 S/PDIF Support Robert Robinson
2002-10-03  7:22               ` Jaroslav Kysela
2002-10-03 11:44                 ` Robert Robinson
2002-10-04 11:43               ` Takashi Iwai
2002-10-04 18:28                 ` Robert Robinson
2002-10-04 19:36                   ` multiple devices per card? Guilhem Tardy
2002-10-04 20:22                     ` Patrick Shirkey
2002-10-05  7:14                       ` Jaroslav Kysela
2002-10-05  4:36                   ` Audiophile 2496 S/PDIF Support James Courtier-Dutton
2002-10-05 12:19                     ` Robert Robinson
     [not found] <200210021457.g92Evdsu029206@smtp.mandrakesoft.com>
2002-10-02 15:25 ` questions for alsa-devel Thierry Vignaud
     [not found] <200210021157.g92Bvvk12578@op.net>
2002-10-02 12:53 ` Takashi Iwai
2002-10-02 13:17   ` Thierry Vignaud
2002-10-02 13:29     ` Takashi Iwai
2002-10-02 13:37       ` Thierry Vignaud
2002-10-02 13:44         ` 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=m27kh1djdd.fsf@vador.mandrakesoft.com \
    --to=tvignaud@mandrakesoft.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@op.net \
    --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 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.