All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langer <martin-langer@gmx.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net, pilo.c@wanadoo.fr
Subject: Re: Testers needed: memio-mmap patch (rme32,rme96,nm256)
Date: Sun, 20 Jun 2004 12:11:35 +0200	[thread overview]
Message-ID: <20040620101135.GA755@tuba.home> (raw)
In-Reply-To: <s5hllikor62.wl@alsa2.suse.de>

On Fri, Jun 18, 2004 at 04:51:33PM +0200, Takashi Iwai wrote:
> Hi,
> 
> the attached patch will fix/simplify the mmap of the devices with the
> mmio buffers, such as rme32, rme96 and nm256.
> If you have one of such devices, please test and report whether it
> works with mmap mode (e.g. aplay -M option).

aplay -M and arecord -M is running fine on rme32 :)

> The patch is to CVS version, but likely can be applied to 1.0.5, too.

And if you are using kernel 2.4.x, you have to tune io_remap_page_range()
in the pcm_native.c patch:

    io_remap_page_range(area->vm_start, runtime->dma_addr + offset,
    			size, area->vm_page_prot)

Ok, let's try fullduplex now...

bye,
martin

-- 
                                     Living on earth may be expensive,
                   but it includes an annual free trip around the sun. 


-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-20 10:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 14:51 Testers needed: memio-mmap patch (rme32,rme96,nm256) Takashi Iwai
2004-06-20 10:11 ` Martin Langer [this message]
2004-07-01 13:44   ` Takashi Iwai
2004-07-01 20:13     ` Martin Langer
2004-07-02 12:50       ` Takashi Iwai
2004-07-05 18:47         ` Martin Langer
2004-07-13 19:54           ` Martin Langer

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=20040620101135.GA755@tuba.home \
    --to=martin-langer@gmx.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pilo.c@wanadoo.fr \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.