All of lore.kernel.org
 help / color / mirror / Atom feed
From: Manuel Jander <manuel.jander@usm.cl>
To: Alien <alien999999999@users.sourceforge.net>,
	alsa-devel <alsa-devel@lists.sourceforge.net>
Subject: Re: Aureal Vortex issues
Date: Mon, 07 Feb 2005 14:55:19 -0300	[thread overview]
Message-ID: <1107798919.3259.16.camel@localhost> (raw)
In-Reply-To: <200502062319.29026.alien999999999@users.sourceforge.net>

Hi Maarten,

On Sun, 2005-02-06 at 23:19 +0100, Alien wrote:
> well, i finally got it working...
> 
> it seems that since you changed the mmio address to a pointer to unsigned int, 
> made the hwwrite wrong since it did a >>2 (on my 64bit platform that should 
> be a >>3 ofcourse... i disabled some other code and it works

AFAIK shifting byte offsets to make them dword offsets should just work
on any platform. Its just plain PCI memory mapped I/O after all. By the
way, the addresses defined in the header files are byte addresses.

Have you tried a newer kernel ? Try a vanilla kernel with minimal patch
contaminants if possible. 
I read that post regarding your emu10k1 oopsing too. AFAIK the emu10k1
uses port i/o instead of mmio. That makes me think that if this oopses
are linked somehow, the problem is either a widespread common mistake or
somewhere deeper in the PCI i/o layer of the kernel. 

> i'll give you the changed files, you do with it what you want:
> 
> not that it's better to define the mmio as a void* so that additions involving 
> that do not have to be >>2 or >>3 or whatever.
> 
> i disabled the a3d routines and the vortex3D (since vortex3D was already 
> disabled with an #if 0 ...

What "#if 0" do you mean ? In the current Alsa version in kernel 2.6.9
the 3D sources are accesible and working for au8830's through the "a3d"
PCM device.
The 3D support code is very well tested. It is not considered unstable.
The problem is that there is no library taking advantage of it (and
coordinate mapping functions are missing).

Anyway, it makes me glad to know that you got working. I'll take at a
look at your code changes ASAP and commit possible patches to the ALSA
list, with credits to you of course.

Best Regards, thanks.
-- 
Manuel Jander
Electronic Engineer



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

       reply	other threads:[~2005-02-07 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <W6056410510107771107660839@asteria.telenet-ops.be>
     [not found] ` <1107714766.3298.10.camel@localhost>
     [not found]   ` <200502062319.29026.alien999999999@users.sourceforge.net>
2005-02-07 17:55     ` Manuel Jander [this message]
2005-02-07 20:10       ` Re: Aureal Vortex issues Alien

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=1107798919.3259.16.camel@localhost \
    --to=manuel.jander@usm.cl \
    --cc=alien999999999@users.sourceforge.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mjander@users.sourceforge.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 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.