mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan <alan@clueserver.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, davem@redhat.com (David S. Miller)
Cc: alan@lxorguk.ukuu.org.uk, ac9410@bellsouth.net,
	torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5.4 sound module problem
Date: Wed, 13 Feb 2002 10:59:25 -0800	[thread overview]
Message-ID: <200202132133.g1DLXPL27236@clueserver.org> (raw)
In-Reply-To: <E16awaG-0004sB-00@the-village.bc.nu>
In-Reply-To: <E16awaG-0004sB-00@the-village.bc.nu>

On Wednesday 13 February 2002 02:24, Alan Cox wrote:
> >    There are PCI drivers using the old sound code. Whether it matters is
> > a more complicated question as these devices use ISA DMA emulation or
> > their own pseudo DMA functionality.
> >
> > The sound layer PCI DMA stuff like a nice project for some kernel
> > janitors :-))
>
> Waste of effort. ALSA will replace the OSS code anyway

When I looked at the code, it looked like a lot more than just the sound code 
needed to be fixed.  I will look at the next patch and see what is left.

  reply	other threads:[~2002-02-13 20:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-13  3:51 Albert Cranford
2002-02-13  3:10 ` Alan
2002-02-13  4:22 ` David S. Miller
2002-02-13  9:26   ` Alan Cox
2002-02-13  9:36   ` David S. Miller
2002-02-12 18:52     ` Gérard Roudier
2002-02-13 10:24     ` Alan Cox
2002-02-13 18:59       ` Alan [this message]
2002-02-13 20:26       ` Linus Torvalds
     [not found] <mailman.1013591941.29105.linux-kernel2news@redhat.com>
2002-02-13 17:21 ` Pete Zaitcev
     [not found] <fa.f4gi5iv.1ikenrc@ifi.uio.no>
     [not found] ` <fa.fo94urv.167g1q5@ifi.uio.no>
2002-02-13  5:03   ` John Weber
2002-02-13  5:18     ` Alan
2002-02-13  9:21       ` Alan Cox
2002-02-13  7:46     ` Miles Lane
  -- strict thread matches above, loose matches on Subject: below --
2002-02-13  2:22 Alan

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=200202132133.g1DLXPL27236@clueserver.org \
    --to=alan@clueserver.org \
    --cc=ac9410@bellsouth.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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

all inboxes | Powered by JetHome®