From: "Russell McGuire" <rmcguire@videopresence.com>
To: "'Kumar Gala'" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Audigy SE / ca0106 driver for PowerPC?
Date: Wed, 31 Jan 2007 07:20:59 -0800 [thread overview]
Message-ID: <000001c7454b$69a25ae0$6405a8c0@absolut> (raw)
In-Reply-To: <0ACC0A3E-9DF3-4927-8F67-E525BA0E6C13@kernel.crashing.org>
After comparing the driver methods to a couple of other PCI drivers that do
work on PowerPC <like the nvidia and ati stuff>, it looks like the methods
for accessing the PCI IO space are very depreciated in this driver..
Would it be safe to assume that if I were to modify the existing
chip->port = pci_resource_start(pcidev,0);
chip->res_port = request_region(chip->port, size);
outl(chip->port+MyReg, data);
To something like:
chip->port = pci_resource_start(pcidev,0);
snd_length = pci_resource_len(pcidev, 0);
snd_port = ioremap(chip->port, length);
outl(port+MyReg, data);
I am not sure if I want to leave the outl in there, perhaps a different
function, or just a direct assignment?
-Russ
-----Original Message-----
From: Kumar Gala [mailto:galak@kernel.crashing.org]
Sent: Wednesday, January 31, 2007 6:53 AM
To: rmcguire@videopresence.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Audigy SE / ca0106 driver for PowerPC?
On Jan 31, 2007, at 6:14 AM, Russell McGuire wrote:
> All,
>
> I recently tried to plugin and use an Audigy SE PCI card with
> 2.6.20 and
> noticed that it would lock up during driver registration.
>
> After a little digging, I found that the interrupt routine and a
> few other
> functions are relying on the x86 inl() / outl() to read from the
> sound card.
>
> Is anyone aware of a PPC port for this driver? Or if it would be
> feasible? I
> haven't ported a driver between architectures before.
>
> Or does the inl() / outl() already have PPC equivalent functions
> and I need
> to be looking for a PCI configuration problem with my system?
We implement these on PPC. Clearly we don't have x86 style port IO,
usually its handled by memory mapped access to a special region of
memory that will be converted into a PCI IO space access.
- k
next prev parent reply other threads:[~2007-01-31 15:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1454.1170226011.9285.linuxppc-embedded@ozlabs.org>
2007-01-31 12:14 ` Audigy SE / ca0106 driver for PowerPC? Russell McGuire
2007-01-31 14:52 ` Kumar Gala
2007-01-31 15:20 ` Russell McGuire [this message]
2007-01-31 15:34 ` Kumar Gala
2007-01-31 21:00 ` Russell McGuire
2007-01-31 21:55 ` Kumar Gala
2007-01-31 22:27 ` Russell McGuire
2007-01-31 22:40 ` Kumar Gala
2007-01-31 23:01 ` Russell McGuire
2007-01-31 23:19 ` Kumar Gala
2007-01-31 23:42 ` Russell McGuire
2007-01-31 23:49 ` Kumar Gala
2007-02-01 14:27 ` 8360E - PCI / DTC Blob Setup Russell McGuire
2007-02-01 14:33 ` Kumar Gala
2007-02-01 17:48 ` Russell McGuire
2007-02-01 18:11 ` Kumar Gala
2007-02-02 2:49 ` Russell McGuire
2007-02-02 6:20 ` Kumar Gala
2007-02-02 13:36 ` Russell McGuire
2007-02-02 15:48 ` Kumar Gala
2007-02-03 5:32 ` Russell McGuire
2007-02-05 1:45 ` Benjamin Herrenschmidt
2007-02-08 3:07 ` Andy Fleming
[not found] ` <000501c74592$2229e060$6405a8c0@absolut>
[not found] ` <53119C53-A3A7-4808-849A-09226BBEAC3B@kernel.crashing.org>
2007-02-01 9:00 ` Audigy SE / ca0106 driver for PowerPC? Russell McGuire
2007-02-01 14:22 ` Kumar Gala
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='000001c7454b$69a25ae0$6405a8c0@absolut' \
--to=rmcguire@videopresence.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).