From: Beng Tan <bengtan1@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: (Re)assignment of PCI BARs
Date: Thu, 27 Aug 2009 19:49:32 +0800 [thread overview]
Message-ID: <664902dd0908270449x24f3ee12k615540ffe22e5b58@mail.gmail.com> (raw)
Hi,
I have an issue relating to allocation of PCI resources in the kernel.
My brief question is ... how do I get the kernel to reassign PCI
resources (if that's not already automatic) and/or is it possible to
explicitly reassign a single BAR of a PCI device?
However, my understanding may be incomplete and this question may not
make sense to those who know the kernel better. So, here's some
background.
-- Start background --
I've connected an external PCI Express card to my laptop, but I am
having PCI resource allocation issues.
I have a PE2L (see http://www.hwtools.net/Adapter/PE2L.html)
connecting my laptop's Express Card slot to a Gigabyte ATI Radeon HD
4550. I got the idea from a DIY Vidock thread (see
http://forum.notebookreview.com/showthread.php?t=397667), and the PE2L
is apparently the same as a ViDock2 (see
http://www.villagetronic.com/vidock2/index.html).
My laptop is a Dell 640m (with integrated Intel graphics), and I'm
trying to find a way to hook up 2 external monitors without having to
buy a new system. Hence the external graphics card idea.
-- End background --
The symptom I'm seeing is that the card has BAR 0 unassigned ...
Region 0: Memory at <unassigned> (64-bit, prefetchable) [disabled]
and indeed, the kernel reports this through dmesg ...
[ 6.147093] PCI: Failed to allocate mem resource
#0:10000000@e0000000 for 0000:0d:00.0
Full logs are available at:
http://208.100.55.9/coldboot_20090827/dmesg.txt
http://208.100.55.9/coldboot_20090827/iomem.txt
http://208.100.55.9/coldboot_20090827/lspci_vv.txt
Doesn't the kernel reassign PCI resources if the BIOS doesnt do a good
enough job? Or is that not the case in my old kernel (2.6.24)?
Is it possible to force a reassignment of the impacted BAR? For
example, I wrote a small module which wrote to the device's PCI
configuration registers to explcitly reassign BAR 0 to 0xc00000000
(and also bit bashed the connecting bridge to do the same) but ... I'm
not sure if I'm doing it correctly.
I believe the hardware is working fine. X was able to find out about a
monitor attached to the device, but that is all.
And, for reference, you can see someone else's lspci output of the
same card in the first post of
http://ubuntuforums.org/archive/index.php/t-1215318.html.
So, any thoughts for things I can try to diagnose this? Should I try
compiling and running a bleeding edge kernel?
Thank you. Any help is much appreciated.
Beng Tan
ThinkLeft
next reply other threads:[~2009-08-27 11:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 11:49 Beng Tan [this message]
2009-08-27 23:19 ` Jesse Barnes
2009-08-28 3:57 ` Beng Tan
2009-08-28 7:13 ` Beng Tan
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=664902dd0908270449x24f3ee12k615540ffe22e5b58@mail.gmail.com \
--to=bengtan1@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®