Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paul Davis <pbd@op.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Re: hdsp on big-endian
Date: Wed, 22 May 2002 15:47:17 +0200	[thread overview]
Message-ID: <s5hoff8fg62.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020522132801.E18131E7CC@Cantor.suse.de>

At Wed, 22 May 2002 09:29:57 -0400,
Paul Davis wrote:
> 
> >> >anyway...  after looking at the hdsp code again, i found that these
> >> >endian conversions are not necessary at all!
> >> >IIRC, readX/writeX already convert the endianess in itself.  thus, the
> >> 
> >> absolutely not. readl/writel on most architectures translate to:
> >> 
> >> 	   *addr = val;
> >> 
> >
> >really?  for example, ppc uses in_le32() for readl(), which implies
> >byte swapping.
> 
> what does CONFIG_APUS do? thats the conditional on which in_le32 is
> used or not. AFAIK, readl is not supposed to have
> endian-characteristics, but if true, that would make the non-APUS ppc
> version totally wrong.

CONFIG_APUS is for amiga.  it's not set usually.
i have no idea about APUS, but it looks like the BE interface.

basically PCI bus is accessed as LE.  that's why in_le32 is used
there.  we can access to io without considration of endianess as long
as using readX/writeX.  (for direct access, you can use __raw_readX()
macros.)


> on x86:
> 
> #define __io_virt(x) ((void *)(x))
> #define readl(addr) (*(volatile unsigned int *) __io_virt(addr))
> #define writel(b,addr) (*(volatile unsigned int *) __io_virt(addr) = (b))

yep, on LE architectures, no conversion is necessary.


Takashi

_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm

  parent reply	other threads:[~2002-05-22 13:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 17:04 hdsp on big-endian Takashi Iwai
2002-05-21 17:22 ` Paul Davis
2002-05-22 11:21   ` Takashi Iwai
2002-05-22 12:25     ` Paul Davis
2002-05-22 12:56       ` Takashi Iwai
2002-05-22 13:29         ` Paul Davis
     [not found]         ` <20020522132801.E18131E7CC@Cantor.suse.de>
2002-05-22 13:47           ` Takashi Iwai [this message]
2002-05-22 13:56             ` Paul Davis
2002-05-23  9:58               ` Takashi Iwai
2002-05-23 14:20                 ` Paul Davis
2002-05-24 16:34                   ` Takashi Iwai

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=s5hoff8fg62.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=pbd@op.net \
    /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