From: oeai <oeai@ya.ru>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: EMU-1212m "no Audiodock - no firmware" patch
Date: Mon, 26 Nov 2012 00:09:30 +0400 [thread overview]
Message-ID: <50B27AFA.8000208@ya.ru> (raw)
In-Reply-To: <CAAMvbhHyG-W-vtu+wpq3JY-Uh-1uuK+5WC6+LJNEG3oy7z=J+A@mail.gmail.com>
Oh, it's nice really!!
Did i understand you correctly - that the ca_cardbus - is the pcmcia bus
support?
So i need just to turn it off and that will solve the problem of waking
up from suspend?
nor should i put it in the end of the init process (so that sequence
would be loaded before it)?
just didn't understand what do you mean @new card@ because it is
actually stopped being supported and now they do the pcie and usb cards
only.
=)
On 25.11.2012 23:05, James Courtier-Dutton wrote:
> Can I help at all?
> I don't have much time spare, but I do have datasheets for some EMU cards.
> The PCMCIA/Cardbus versions need a special startup sequence before you
> can write or read any other registers.
> Failing to follow the startup sequence causes a PCI fault on the bus
> when you write to other registers on the card.
> I have not read the code recently, but I think that is what
> "ca_cardbus_chip = 1".
> For any new cards, you can try removing it, and if you get a PCI fault
> or hang on start up, put it back in.
>
--
RA
OE
AI
next prev parent reply other threads:[~2012-11-25 20:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 22:18 EMU-1212m "no Audiodock - no firmware" patch oeai
2012-11-22 17:17 ` Takashi Iwai
2012-11-22 20:09 ` oeai
2012-11-23 11:23 ` Takashi Iwai
2012-11-23 20:13 ` Re oe to ta about latest drivers and so on: " oeai
2012-11-25 19:05 ` James Courtier-Dutton
2012-11-25 20:09 ` oeai [this message]
2012-12-29 2:45 ` oeai
2012-12-29 2:52 ` oeai
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=50B27AFA.8000208@ya.ru \
--to=oeai@ya.ru \
--cc=alsa-devel@alsa-project.org \
--cc=james.dutton@gmail.com \
--cc=tiwai@suse.de \
/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