All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur Marsh <arthur.marsh@internode.on.net>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: alsa-user@lists.sourceforge.net,
	ALSA devel <alsa-devel@alsa-project.org>,
	Armin ranjbar <zoup@zoup.org>
Subject: Re: [Alsa-user] Pc Speaker
Date: Fri, 23 May 2008 09:24:08 +0930	[thread overview]
Message-ID: <483607A0.3000504@internode.on.net> (raw)
In-Reply-To: <4835DBA0.90401@keyaccess.nl>

Rene Herman wrote, on 2008-05-23 06:16:
> On 22-05-08 14:01, Arthur Marsh wrote:
> 
>> under Debian unstable, by overwriting the unpacked Debian source tarball.
> 
> I'm afraid you lost me here. I have little clue about Debian.
> 
> Rene.

When one installs the "alsa-source" package on Debian and unpacks the 
resulting /usr/src/alsa-driver.tar.bz2 file, it ends up in a directory 
under /usr/src/modules.

Normally one would also have the kernel source unpacked into 
/usr/src/linux, then run:

make-kpkg --initrd linux-image modules-image

to compile a kernel and whatever modules packages were installed (e.g. ALSA)

I unpacked the Mercurial snapshot, then did a cp -r of the snapshot to 
the directory underneath /usr/src/modules where the alsa drivers were 
unpacked so that I could still use the Debian build process to compile 
the Mercurial snapshot of ALSA.

Arthur.

      reply	other threads:[~2008-05-22 23:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080513110322.030a5386.zoup@zoup.org>
     [not found] ` <48296CFF.5000207@keyaccess.nl>
     [not found]   ` <20080513151425.448369e8.zoup@zoup.org>
2008-05-13 11:14     ` [Alsa-user] Pc Speaker Rene Herman
2008-05-13 11:20       ` Takashi Iwai
2008-05-13 11:32         ` Rene Herman
2008-05-13 12:25           ` Rene Herman
2008-05-22 12:01       ` Arthur Marsh
2008-05-22 20:46         ` [Alsa-user] " Rene Herman
2008-05-22 23:54           ` Arthur Marsh [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=483607A0.3000504@internode.on.net \
    --to=arthur.marsh@internode.on.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=rene.herman@keyaccess.nl \
    --cc=zoup@zoup.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 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.