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: Thu, 23 May 2002 11:58:49 +0200 [thread overview]
Message-ID: <s5h661ffana.wl@alsa2.suse.de> (raw)
In-Reply-To: <E17AWZX-00026H-00@usw-sf-list1.sourceforge.net>
At Wed, 22 May 2002 09:56:28 -0400,
Paul Davis wrote:
>
> >basically PCI bus is accessed as LE. that's why in_le32 is used
>
> OK, well apparently on OS X, either RME didn't use standard macros for
> this (most likely), or there are no standard macros for this.
>
> >there. we can access to io without considration of endianess as long
> >as using readX/writeX.
>
> Sounds like it, yes. Very nice.
ok, then we can erase stuffs cpu_to_xxx and vice versa.
but still one thing is not certain. what does the following (in
snd_hdsp_initialize_firmware) set?
#ifdef SNDRV_BIG_ENDIAN
hdsp_write(hdsp, HDSP_jtagReg, HDSP_BIGENDIAN_MODE);
#endif
does it switch the access to big-endian? if yes, then we need
cpu_to_xxx things there (to revert the conversion in readX/writeX), or
use __raw_readX/writeX for access.
well, anyway a tester with ppc machine is wanted to confirm this...
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
next prev parent reply other threads:[~2002-05-23 9:58 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
2002-05-22 13:56 ` Paul Davis
2002-05-23 9:58 ` Takashi Iwai [this message]
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=s5h661ffana.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