From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA Driver for Sparc DBRI chips
Date: Sat, 18 Dec 2004 15:15:09 +0000 [thread overview]
Message-ID: <20041218151509.GA13178@palantir8> (raw)
In-Reply-To: <s5hpt22ni23.wl@alsa2.suse.de>
Takashi,
Sorry for the late reply. I was travelling and forgot to check alsa-devel
(shame on me!). Besides, it seems quite hard to get hold of a sparc32 to
test on while on the road.
On Thu, Nov 25, 2004 at 03:01:56PM +0100, Takashi Iwai wrote:
> I modified some codes to adapt to the latest 2.6.10-rc2, and reduced
> compile warnings (just checked with the cross-compile environment.)
> ALso, the spin_lock() is changed to spin_lock_irq() in the prepare
> callback since the recent version is it became non-atomic.
> The patch is below.
>
> If you think your driver is mature to merge to Linux kernel, let me
> know. Otherwise I'll merge it to alsa-driver tree which is regarded
> as the experimental tree and not submitted to mainstream kernel.
I consider the code still expermental, so alsa-driver is okay. I'd like some
other sparc folks to try it before it gets submitted to mainstream, even if
it works okay for me.
> BTW, the build environment of alsa-driver for sparc has been fixed
> recently on CVS.
Thanks for the tip. I'll check it out.
Martin
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-12-18 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-21 9:50 ALSA Driver for Sparc DBRI chips Martin Habets
2004-11-25 14:01 ` Takashi Iwai
2004-11-25 15:55 ` Takashi Iwai
2004-12-01 13:58 ` Takashi Iwai
2004-12-18 15:15 ` Martin Habets [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=20041218151509.GA13178@palantir8 \
--to=errandir_news@mph.eclipse.co.uk \
--cc=alsa-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox