All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Mikhail Ramendik <mr@ramendik.ru>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Compiling the newest code for testing?
Date: Fri, 07 Jan 2005 19:39:31 +0100	[thread overview]
Message-ID: <s5hmzvlulr0.wl@alsa2.suse.de> (raw)
In-Reply-To: <200501072127.38967.mr@ramendik.ru>

At Fri, 7 Jan 2005 21:27:38 +0300,
Mikhail Ramendik wrote:
> 
> > > - Is it OK to compile this kernel code by merely copying the relevant
> > > directories (sound [except for sound/oss] and include/sound) from the
> > > alsa tree into the kernel tree? I run an RPM-based system, and would like
> > > to keep the existing approach to kernel building (full RPM rebuild)
> > > alive; it's slow but reliable.
> >
> > Not always.  The ALSA cvs may contain the codes for the very latest
> > kernel (rc or mm).  Copying the files to kernel might not work when
> > the kernel function / API is changed.  The difference is usually
> > absorbed by patches in alsa-driver tree.
> 
> Which kernel is 1.0.8rc2 for? There apparently is no recent -rc at the moment. 
> If it's against an -mm version, I can compile that too, at least for the alsa 
> tests. I just need to be sure which kernel version it's tied to.

Basically, alsa-kernel is for the latest vanilla kernel.
Not sure whether it works with 2.6.10-mm tree now although I think it
should be fine, too.

> > > And an i8x0-specific question: in the above-mentioned current code,
> > > should output to hw:0,0 go only to analog, or to both analog and spdif?
> >
> > Analog only.
> >
> > Basically, you should avoid to access "hw:0,0".  If you want to output
> > to analog front, you can use "front", instead.  Similarly, for spdif,
> > use "spdif" (or "iec958").
> 
> But OSS emulation is needed for some of the stuff I use, and that writes to 
> hw:0,0 . I know I should be searching for fixed on the other end as well.

Then avoid OSS ;)

Or, you can assign hw:0,4 to /dev/adsp with a module option.
See OSS-Emulation.txt for details.


Takashi


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt

      reply	other threads:[~2005-01-07 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-07  2:25 Compiling the newest code for testing? Mikhail Ramendik
2005-01-07 11:16 ` Takashi Iwai
2005-01-07 18:27   ` Mikhail Ramendik
2005-01-07 18:39     ` Takashi Iwai [this message]

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=s5hmzvlulr0.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mr@ramendik.ru \
    /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.