Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Amaury Jacquot <sxpert@esitcom.org>, Alsa-devel@lists.sourceforge.net
Subject: Re: alsa and kernel 2.6
Date: Fri, 16 Jan 2004 20:01:14 +0000	[thread overview]
Message-ID: <4008430A.7070408@superbug.demon.co.uk> (raw)
In-Reply-To: <s5h8yk7ena8.wl@alsa2.suse.de>

Takashi Iwai wrote:
> At Fri, 16 Jan 2004 13:02:39 +0000,
> James Courtier-Dutton wrote:
> 
>>Amaury Jacquot wrote:
>>
>>>any chance the alsa that is in 2.6 would get updated to the latest 
>>>stable version (1.0.1) ?
>>>this would allow me to test kernel 2.6 on my carpc
>>>
>>>also, I didn't find any changelog in the alsa tree ...
>>>
>>>
>>
>>For test purposes, try option 2 on 
>>http://alsa.opensrc.org/index.php?page=AlsaBuild2.6
>>
>>It tells you how to merge 1.0.1 with the 2.6 kernel.
> 
> 
> the current version of alsa-driver can be built directly with the 2.6
> kernel tree.  there was a bug regading the module versioning, and i
> fixed it right now.
> 
> 
> Takashi
> 
> 
Is there a tar ball of alsa-driver that works with 2.6 kernel ?
The latest 1.0.1 tar ball does not work.
If you think it should work, I will try again, and post the bug output.

Cheers
James



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  reply	other threads:[~2004-01-16 20:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-16 12:57 alsa and kernel 2.6 Amaury Jacquot
2004-01-16 13:02 ` James Courtier-Dutton
2004-01-16 18:55   ` Takashi Iwai
2004-01-16 20:01     ` James Courtier-Dutton [this message]
2004-01-19 11:08       ` 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=4008430A.7070408@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=Alsa-devel@lists.sourceforge.net \
    --cc=sxpert@esitcom.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox