From: Clemens Ladisch <clemens@ladisch.de>
To: "Christian P. Schmidt" <schmidt@digadd.de>
Cc: linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] How can PCI resource allocation fail?
Date: Fri, 13 Mar 2009 08:44:26 +0100 [thread overview]
Message-ID: <49BA0EDA.4080606@ladisch.de> (raw)
In-Reply-To: <49B9959F.1080705@digadd.de>
Christian P. Schmidt wrote:
> I'm toying with the alsa-driver for the Creative Labs X-Fi. I'm working
> on the PCI Express version of this card,
... which isn't supported ...
> [46833.487588] cannot allocate the port
> [46833.487594] CA0106: probe of 0000:04:00.0 failed with error -16
> ...
> Region 0: Memory at f9ffc000 (32-bit, non-prefetchable) [size=16K]
... because this I/O range is memory-mapped; the driver knows only about
models with regular I/O ports. (This has nothing to do with the PCI-E
bridge; the X-Fi chip itself is a different model.)
Best regards,
Clemens
next prev parent reply other threads:[~2009-03-13 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-12 23:07 How can PCI resource allocation fail? Christian P. Schmidt
2009-03-13 2:36 ` Robert Hancock
2009-03-13 7:44 ` Clemens Ladisch [this message]
2009-03-13 8:24 ` [alsa-devel] " Takashi Iwai
2009-03-13 10:24 ` Vedran Miletić
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=49BA0EDA.4080606@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schmidt@digadd.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