mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: alan@clueserver.org
Cc: John Weber <john.weber@linuxhq.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.4 sound module problem
Date: 12 Feb 2002 23:46:13 -0800	[thread overview]
Message-ID: <1013586374.412.1.camel@turbulence.megapathdsl.net> (raw)
In-Reply-To: <200202130752.g1D7qDL22868@clueserver.org>
In-Reply-To: <fa.f4gi5iv.1ikenrc@ifi.uio.no> <fa.fo94urv.167g1q5@ifi.uio.no> <3C69F385.5050207@linuxhq.com>  <200202130752.g1D7qDL22868@clueserver.org>

On Tue, 2002-02-12 at 21:18, Alan wrote:
> On Tuesday 12 February 2002 21:03, John Weber wrote:

<snip>

> > This is correct.  It has been a policy to use pci_alloc_consistent
> > instead of kmalloc/getfreepages and virt_to_bus, 2.5 is enforcing it now.
> 
> By breaking sound (in dmabuf and sound modules), cardbus (lots of places), 
> and who knows what else.
> 
> "grep -r virt_to_bus | less" shows jut how bad it is going to be...

I checked, there are 1069 occurrences.

	Miles


  parent reply	other threads:[~2002-02-13  7:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 [this message]
     [not found] <mailman.1013591941.29105.linux-kernel2news@redhat.com>
2002-02-13 17:21 ` Pete Zaitcev
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
2002-02-13 20:26       ` Linus Torvalds
  -- 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=1013586374.412.1.camel@turbulence.megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=alan@clueserver.org \
    --cc=john.weber@linuxhq.com \
    --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

all inboxes | Powered by JetHome®