From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andy Pfiffer <andyp@osdl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.5.29: some compilation fixes for irq frenzy [OSS + i8x0 audio]
Date: Thu, 1 Aug 2002 01:02:17 +0200 [thread overview]
Message-ID: <20020801010217.K10436@suse.de> (raw)
In-Reply-To: <1028160492.13008.7.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Thu, Aug 01, 2002 at 01:08:12AM +0100
On Thu, Aug 01, 2002 at 01:08:12AM +0100, Alan Cox wrote:
> Rusty submitted a much better patch for this - deleting all the old OSS
> ISA drivers, so that people can just fix and use the ALSA code instead.
> I'm not saying don't analyse the locks and interrupt paths and fix the
> OSS audio for ISA stuff, just that it might not be the best use of time
> even if you do get it sorted out.
Are there any OSS drivers for any particular cards for which we don't have
an equivalent ALSA driver ? If we're ultimately going to be dropping
any of the OSS drivers, I'd rather know about it so I don't waste time
pushing the ~200kb of patches in that area I'm currently carrying
towards Linus. (Given that most of them don't compile right now due to
the collateral damage from the cli() etc changes , I'd *love* to take
the lazy^Weasy option and just drop them)
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-07-31 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 20:56 [PATCH] 2.5.29: some compilation fixes for irq frenzy [OSS + i8x0 audio] Andy Pfiffer
2002-07-30 22:25 ` Alan Cox
2002-07-30 21:19 ` Andy Pfiffer
2002-07-30 22:47 ` Alan Cox
2002-07-30 21:35 ` Andy Pfiffer
2002-07-31 21:50 ` Andy Pfiffer
2002-08-01 0:08 ` Alan Cox
2002-07-31 23:02 ` Dave Jones [this message]
2002-08-01 0:41 ` Alan Cox
2002-08-01 0:08 ` Alan Cox
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=20020801010217.K10436@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andyp@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).