linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: user <igor.florea@topex.ro>
To: linux-hotplug@vger.kernel.org
Subject: Compact PCI hotplug-ed wrong?
Date: Thu, 29 Dec 2005 13:37:10 +0000	[thread overview]
Message-ID: <200512291736.49388.igor.florea@topex.ro> (raw)

 Hi all
I have a problem in detecting hotpluged Compact PCI cards..
first of all .. i modified the cpci_generic.c and cpci_hotplug_core.c drivers 
in order get hotswap working..
now i can remove the card and when i lspci device is not seen
when i plug the card..i can see it with a lspci but it has the IRQ 255 and 
that is not good..
when i insmod my card driver named SIM ..i get negative return from 
pci_enable_device function
here is my dmesg :

<7>[ 4299.720271] cpci_hotplug: check_slots - looking at slot 02:0a
<7>[ 4299.720291] cpci_hotplug: check_slots - looking at slot 02:09
<7>[ 4299.720316] cpci_hotplug: check_slots - slot 02:09 inserted
<7>[ 4299.720339] cpci_hotplug: check_slots - slot 02:09 HS_CSR (1) = 0008
<7>[ 4299.720351] cpci_hotplug: check_slots - configuring slot 02:09
<7>[ 4299.720363] cpci_hotplug: cpci_configure_slot - enter
<7>[ 4299.720376] cpci_hotplug: pci_dev null, finding 02:09:0
<7>[ 4299.720388] cpci_hotplug: pci_dev still null
<7>[ 4299.720512] cpci_hotplug: cpci_configure_slot: pci_scan_slot returned 1
<7>[ 4299.724038] SIM::sim_probe: sim_probe called
<4>[ 4299.724049]
<3>[ 4299.724141] PCI: Device 0000:02:09.0 not available because of resource 
collisions
<7>[ 4299.724156] SIM::sim_probe: unable to initialize PCI device
<4>[ 4299.724163]
<6>[ 4299.724271] PCI: Bridge: 0000:03:0c.0
<6>[ 4299.724281]   IO window: disabled.
<6>[ 4299.724297]   MEM window: disabled.
<6>[ 4299.724311]   PREFETCH window: disabled.
<6>[ 4299.724328] PCI: Bridge: 0000:02:0c.0
<6>[ 4299.724336]   IO window: disabled.
<6>[ 4299.724350]   MEM window: disabled.
<6>[ 4299.724362]   PREFETCH window: disabled.
<7>[ 4299.724379] cpci_hotplug: cpci_configure_slot - exit
<7>[ 4299.724392] cpci_hotplug: check_slots - finished configuring slot 02:09
<7>[ 4299.724416] cpci_hotplug: check_slots - slot 02:09 HS_CSR (2) = 0008
<7>[ 4299.724472] cpci_hotplug: check_slots - slot 02:09 HS_CSR (3) = 0000
<7>[ 4299.724488] cpci_hotplug: inserted=1, extracted=0, extracting=0

SIM is my card driver..
can anybody tell me what is the problem and how to solve it?
thanks 


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

                 reply	other threads:[~2005-12-29 13:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200512291736.49388.igor.florea@topex.ro \
    --to=igor.florea@topex.ro \
    --cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).