mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan <alan@clueserver.org>
To: Albert Cranford <ac9410@bellsouth.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.4 sound module problem
Date: Tue, 12 Feb 2002 19:10:08 -0800	[thread overview]
Message-ID: <200202130544.g1D5i4L22169@clueserver.org> (raw)
In-Reply-To: <3C69E2C7.3E749061@bellsouth.net>
In-Reply-To: <3C69E2C7.3E749061@bellsouth.net>

On Tuesday 12 February 2002 19:51, Albert Cranford wrote:
> Not sure if this was the same message I received. but here
> is the patch I used to get around my sound problem in
> 2.5.4.

Are you sure this is correct?  include/asm/io.h seems to indicate that i/o 
addresses for PCI may not map correctly.  The sound card I am using is PCI, 
not ISA.

Documentation/DMA-mapping.txt says that virt_to_bus is completly depreciated 
and nothing should be using it.  Well, grepping the kernel source shows that 
quite a bit still uses it.

What it looks like, on first glance, is that virt_to_bus  was changed for pci 
devices to give this error message.  (Since that symbol goes nowhere.)  That 
effects a number of things, not just sound. (A whole bunch of cardbus drivers 
I would guess...)

When was this change made? It appears as if they missed a few bits.

Comment: 2.5.4 has been more than a bit rough.  Rarely do i see more than one 
patch needed just to get it to compile. Not trying to be bitchy about it. 
Just a wee bit frustrated...

> Linus, please apply to 2.5.5 pre1
> Later,
> Albert
> --- linux/drivers/sound/dmabuf.c.orig   Tue Feb 12 10:12:59 2002
> +++ linux/drivers/sound/dmabuf.c        Tue Feb 12 10:15:06 2002
> @@ -113,7 +113,7 @@
>                 }
>         }
>         dmap->raw_buf = start_addr;
> -       dmap->raw_buf_phys = virt_to_bus(start_addr);
> +       dmap->raw_buf_phys = isa_virt_to_bus(start_addr);
>
>         for (page = virt_to_page(start_addr); page <=
> virt_to_page(end_addr); page++) mem_map_reserve(page);

  reply	other threads:[~2002-02-13  4:29 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 [this message]
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
     [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=200202130544.g1D5i4L22169@clueserver.org \
    --to=alan@clueserver.org \
    --cc=ac9410@bellsouth.net \
    --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®