[Bug 2944] Cardbus cards not seen on ti1620 cardbus controler
bugme-daemon at bugzilla.kernel.org
bugme-daemon at bugzilla.kernel.org
Wed Apr 19 18:52:03 EDT 2006
http://bugzilla.kernel.org/show_bug.cgi?id=2944
bk at suse.de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linux-
| |pcmcia at lists.infradead.org
------- Additional Comments From bk at suse.de 2006-04-19 15:51 -------
Bug #5557 is also about the same problem some related info can be found there.
Looking thru the mail archives of February, March and April (until today) of
linux-pcmcia on http://lists.infradead.org/pipermail/linux-pcmcia/ , I have
found five additional laptops which should be fixed with this patch:
Alex Kavanagh
- HP DV1448:
Bus: primary=00, secondary=06, subordinate=06, sec-latency=216
Bus: primary=06, secondary=07, subordinate=0a, sec-latency=176
http://lists.infradead.org/pipermail/linux-pcmcia/2006-April/003492.html
Nicolas Bellido
- Toshiba Satellite Pro A60 with TI PCI1440 Cardbus controller:
Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
http://lists.infradead.org/pipermail/linux-pcmcia/2006-March/003350.html
Chris Lu
- Unknown machine based on nVidia Corporation nForce3 Host Bridge (rev a4):
Bus: primary=00, secondary=02, subordinate=02, sec-latency=128
Bus: primary=02, secondary=07, subordinate=0a, sec-latency=176
http://lists.infradead.org/pipermail/linux-pcmcia/2006-March/003356.html
Jeremy Johnson
- Kyocera KPC650:
Bus: primary=00, secondary=05, subordinate=05, sec-latency=64
Bus: primary=05, secondary=06, subordinate=09, sec-latency=176
http://lists.infradead.org/pipermail/linux-pcmcia/2006-April/003459.html
Diego Martín
- Unkonwn ICH6 Machine without lspci -vv but fixed also with pci=assign-busses:
0000:02:04.0 CardBus bridge: ENE Technology Inc CB-710/2/4 Cardbus Controller
http://lists.infradead.org/pipermail/linux-pcmcia/2006-March/003419.html
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the linux-pcmcia
mailing list