public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] 2.4.18-rc1 es1370 fix
Date: Sat, 16 Feb 2002 10:31:28 +0100	[thread overview]
Message-ID: <3C6E26F0.3070808@wanadoo.fr> (raw)
In-Reply-To: <20020214161730.A8112@bytesex.org>

Gerd Knorr wrote:
>   Hi,
> 
> This patch (against 2.5.5-pre1) fixes the es1370 driver (the virt_to_bus thing).

The same applies to 2.4.18-rc1

----------------------------- cut here --------------------------
--- linux.orig/drivers/sound/es1370.c	Sat Feb 16 09:33:37 2002
+++ linux/drivers/sound/es1370.c	Sat Feb 16 09:41:02 2002
@@ -374,6 +374,10 @@
  		unsigned subdivision;
  	} dma_dac1, dma_dac2, dma_adc;

+ 
/* The following buffer is used to point the phantom write channel to. */
+ 
unsigned char *bugbuf_cpu;
+ 
dma_addr_t bugbuf_dma;
+
  	/* midi stuff */
  	struct {
  		unsigned ird, iwr, icnt;
@@ -392,13 +396,6 @@

  static LIST_HEAD(devs);

-/*
- * The following buffer is used to point the phantom write channel to,
- * so that it cannot wreak havoc. The attribute makes sure it doesn't
- * cross a page boundary and ensures dword alignment for the DMA engine
- */
-static unsigned char bugbuf[16] __attribute__ ((aligned (16)));
-
  /* 
--------------------------------------------------------------------- */

  static inline unsigned ld2(unsigned int x)
@@ -2649,8 +2646,9 @@
  	outl(s->ctrl, s->io+ES1370_REG_CONTROL);
  	outl(s->sctrl, s->io+ES1370_REG_SERIAL_CONTROL);
  	/* point phantom write channel to "bugbuf" */
+ 
s->bugbuf_cpu = pci_alloc_consistent(pcidev,16,&s->bugbuf_dma);
  	outl((ES1370_REG_PHANTOM_FRAMEADR >> 8) & 15, s->io+ES1370_REG_MEMPAGE);
- 
outl(virt_to_bus(bugbuf), s->io+(ES1370_REG_PHANTOM_FRAMEADR & 0xff));
+ 
outl(s->bugbuf_dma, s->io+(ES1370_REG_PHANTOM_FRAMEADR & 0xff));
  	outl(0, s->io+(ES1370_REG_PHANTOM_FRAMECNT & 0xff));
  	pci_set_master(pcidev);  /* enable bus mastering */
  	wrcodec(s, 0x16, 3); /* no RST, PD */
@@ -2717,6 +2715,7 @@
  	unregister_sound_mixer(s->dev_mixer);
  	unregister_sound_dsp(s->dev_dac);
  	unregister_sound_midi(s->dev_midi);
+ 
pci_free_consistent(dev, 16, s->bugbuf_cpu, s->bugbuf_dma);
  	kfree(s);
  	pci_set_drvdata(dev, NULL);
}

-- 
------------------------------------------------
  Pierre Rousselet <pierre.rousselet@wanadoo.fr>
------------------------------------------------


      parent reply	other threads:[~2002-02-16  9:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-14 15:17 [PATCH] es1370 fix Gerd Knorr
2002-02-14 17:27 ` Thomas Sailer
2002-02-16  9:31 ` Pierre Rousselet [this message]

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=3C6E26F0.3070808@wanadoo.fr \
    --to=pierre.rousselet@wanadoo.fr \
    --cc=kraxel@bytesex.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