From: Takashi Iwai <tiwai@suse.de>
To: Laurent Canet <lc@tekila.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Non-coherent memory mapped devices
Date: Wed, 19 Mar 2003 12:48:02 +0100 [thread overview]
Message-ID: <s5h4r5ztw5p.wl@alsa2.suse.de> (raw)
In-Reply-To: <20030318204808.66a39ed7.lc@tekila.org>
Hi,
At Tue, 18 Mar 2003 20:48:08 +0100,
Laurent Canet wrote:
>
> Hi,
>
> On the HPPA architecture, devices (including sound ones) are memory-mapped.
> On particular machines, memory access to devices are not consistent,
> i.e. data wrote to memory could be cached by the CPU, thus inacessible
> to the device.
doesn't ioremap_nocache() suffice for such a case?
Takashi
-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink?
You could win a Tablet PC. Get a free Tablet PC hat just for playing.
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
prev parent reply other threads:[~2003-03-19 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-18 19:48 Non-coherent memory mapped devices Laurent Canet
2003-03-18 19:33 ` Jaroslav Kysela
2003-03-19 11:48 ` Takashi Iwai [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=s5h4r5ztw5p.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=lc@tekila.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