OK list, here's an update. I had my software engineer do some tests on
his system, and this is what I get when he powers on the target device:
[ 149.626692] pci 0000:01:00.0: [1a39:0004] type 0 class 0x000000
[ 149.626721] pci 0000:01:00.0: reg 10: [mem 0x00000000-0x000fffff 64bit]
[ 149.626741] pci 0000:01:00.0: reg 18: [mem 0x00000000-0x000fffff 64bit]
[ 149.626761] pci 0000:01:00.0: reg 20: [mem 0x00000000-0x00000fff 64bit]
[ 149.631745] pcieport 0000:00:01.0: BAR 14: assigned [mem
0xc0800000-0xc0afffff]
[ 149.631837] gn_pcie 0000:01:00.0: device not available (can't reserve
[mem 0x00000000-0x000fffff 64bit])
A simple lspci shows the device in the list, but since the driver failed
to register the device, it is inaccessible to his applications.
Any ideas?
-Frank
On Thu, 18 Apr 2013 19:59:11 -0700, Frank Rizzo
<thefrankrizzo@xxxxxxxxxxx> wrote:
Hey list.
I'm working on a driver for a device that's external from the PC. It's
connected to the PC via a weird cable that connects to a PCIE card
inside the case that appears to be nothing other than glue logic to
allow the signals from the cable to be tossed onto the bus.
When the external device is powered off during boot, nothing is found.
hwinfo doesn't find it, lspci doesn't find it, etc. If you power on
the device BEFORE booting, everything is found, and it works fine. And
lastly, if you power it on AFTER Linux has booted, you still can't find
it. I've tried echoing "1" to rescan, and everything else that I could
find via Google search.
So, what are my options here? I'm not allergic to adding code to the
driver to scan for the device periodically, if I knew HOW to find it.
And, once found, how do I get it registered?
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
