Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Matthias Saou <matthias@rpmforge.net>
Cc: Jeremy Sanders <jsanders@teklinks.com>,
	jason@corekin.no-ip.com, alsa-user@lists.sourceforge.net,
	alsa-devel@lists.sourceforge.net,
	matthias.saou@est.une.marmotte.net
Subject: Re: [Alsa-user] alsa cvs, redhat9, kernel 2-4-20-8
Date: Mon, 07 Apr 2003 12:19:38 +0200	[thread overview]
Message-ID: <s5hznn2r4n9.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030405120028.6812ba7e.matthias@rpmforge.net>

At Sat, 5 Apr 2003 12:00:28 +0200,
Matthias Saou wrote:
> 
> "Jeremy Sanders" <jsanders@teklinks.com> wrote :
> 
> > Maybe matthias.saou@est.une.marmotte.net is the one to ask. He's the one
> > who built the freshrpm package that works with the redhat 9 kernel.
> > Maybe he can shed some light on what he had to do.
> > 
> > Matthias,
> > 
> > Do you have any ideas about this?
> 
> Yes I have :-)
> I didn't think of it myself though, someone had suggested me this solution
> a while back for the latest Rawhide kernels. Take a look at my spec file if
> you like: http://freshrpms.net/packages/builds/index.html?build=alsa-driver
> 
> The part that "fixes" the schedule_work problem is:
> 
> # Temporary Rawhide kernel workaround - Disable ALSA workqueue wrapper
> touch include/linux/workqueue.h
> 
> I don't really know the implications of doing this, but I'm open to any
> suggestions or better ways of getting the kernel modules to work.

the current alsa code checks the existence of __WORK_INITIALIZER
macro.  if it's defined, no wrapper function is used.
in rh's include/linux/workqueue.h, is this macro defined?


btw, alsa-devel is the suitable place for such a problem.
i added a cc.


ciao,

Takashi


-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb: 
Dedicated Hosting for just $79/mo with 500 GB of bandwidth! 
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/

       reply	other threads:[~2003-04-07 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <se8e13a5.075@mail.teklinks.com>
     [not found] ` <20030405120028.6812ba7e.matthias@rpmforge.net>
2003-04-07 10:19   ` Takashi Iwai [this message]
2003-04-07 10:27     ` [Alsa-user] alsa cvs, redhat9, kernel 2-4-20-8 Matthias Saou
2003-04-07 15:44       ` Takashi Iwai
2003-04-09  4:58     ` Lance A. Brown

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=s5hznn2r4n9.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=alsa-user@lists.sourceforge.net \
    --cc=jason@corekin.no-ip.com \
    --cc=jsanders@teklinks.com \
    --cc=matthias.saou@est.une.marmotte.net \
    --cc=matthias@rpmforge.net \
    /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