Samuel S Chessman <[EMAIL PROTECTED]> writes:
> In building and running jack 0.94 from current tar, segfault traced to
> alsa_driver at snd_pcm_hw_params_set_rate_near (line 388).
>
> This occurs when switching to 16 bit or starting with 16 bit (-S option)
>
> This is caused by snd_pcm_hw_params
eleased in 2.6.[12345]. No one should get hung up by that. Right
now, 2.6.0 needs stability.
Regards,
--
Jack O'Quin
Austin, Texas
---
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more p
l meter is already available and
> working.
>
> It's very simple to add other *-meters, scopes, etc.
That's great!
Is there any user-level documentation for all this cool stuff?
--
Jack O'Quin
Austin, Texas, USA
---
Thi
Takashi Iwai <[EMAIL PROTECTED]> writes:
> I would like to confirm the consensus about $SUBJECT.
> Does anybody still have objections against this action?
I have withdrawn my objections.
Compatibility with de facto kernel standards is a good reason to make
this change.
--
> On 11 Oct 2002, Jack O'Quin wrote:
> > Are you saying that the "snd_" prefix violates standard Linux
> > kernel rules for device driver options? Did the kernel developers
> > request this change?
Jaroslav Kysela <[EMAIL PROTECTED]> writes:
&g
> Jack O'Quin wrote:
> > Can someone please explain what terrible problem we're trying to solve
> > that justifies introducing *any* breakage at all?
>
> > ALSA is part of the 2.5 kernel now. It is mainstream Linux software,
> > good technology, neede
se days.
Since 0.5, which *is* a release, is "no longer supported", what are
ordinary users expected to run? OSS?
ALSA is part of the 2.5 kernel now. It is mainstream Linux software,
good technology, needed by many users. Isn't
g, so even this may be an improvement.
The proposal permits appropriately programmed applications to do
something useful. This behavior conforms to both the letter and
spirit of the X/Open standard, as far as I can see.
So, I think the change *should* be made, even at this late stage of
the rele
people to hassle
with fixing something that's not broken in the first place.
Regards,
--
Jack O'Quin
Austin, Texas, USA
---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Matthias Saou <[EMAIL PROTECTED]> writes:
> All this will get so much easier once stable kernels used by Linux
> distributions come with ALSA by default ;-)
Sure will.
Providing we stay focused on maintaining binary compatibility... :-)
--
Jack O'Quin
Austin,
don't do this"), and not in the broader meanings of
"obstructive" or "pessimistic".
You're doing an important job, and we all appreciate it.
Regards,
--
Jack O'Quin
Austin, Texas, USA
http://www.stellajazz.com
---
or rc3 compatible library and add an
> autoconfiguration code to alsa.m4. My suggestion is to use /opt/alsa/rc3
> directory for this job. Comments?
--
Jack O'Quin
Austin, Texas, USA
http://www.stellajazz.com
---
This SF.NET email is
tions in future. The compatible library
>will be built when '--with-compat-rc3' argument is passed to the
>configure script in alsa-lib. This solution allows keeping binary
>compatibility and allows to update alsa-lib with recent one (built
> without --with-
13 matches
Mail list logo
