Cardbus bridge detected, but attached devices are not

[casm]

`listdev' detects the Cardbus controller in my WebDT 366 (Geode) but not the devices attached to it (Cisco Aironet 350).

device Bridge (CardBus bridge) [6|7|0]

vendor 104c: Texas Instruments device ac55: PCI1520 PC card Cardbus Controller

device Bridge (CardBus bridge) [6|7|0]

vendor 104c: Texas Instruments device ac55: PCI1520 PC card Cardbus Controller

[anevilyak]

That's because listdev simply lists what PCI reports as being on the bus. It has no bearing as to whether or not there is in fact a driver supporting those devices. In the case of cardbus, we currently don't have one.

[anevilyak]

I stand corrected, we do have a cardbus driver (c.f. ticket #1086). Listdev however will currently only list what's on the PCI bus itself, it doesn't probe any other busses.

[colin]

Replying to anevilyak:

I stand corrected, we do have a cardbus driver (c.f. ticket #1086). Listdev however will currently only list what's on the PCI bus itself, it doesn't probe any other busses.

Ticket #1086 is somewhat misleading. In general, there is no CardBus support in the sense of anyone can use hardware with it. What ticket #1086 states is, that during PCI initialization CardBus bridges are detected (so they showup in listdev) but not configured in any way (no powering up, no scanning of connected devices, etc.). Detection of CardBus bridges needs special code during PCI init (CardBus Bridges have their very own PCI header format) this is what ticket #1086 refers, to. Going to add this information to #1086 to prevent future misleadings. Thus leaving this ticket in enhancement state is valid.

[thetick]

Just need to know when CardBus support is added. I would like to use a PCMCIA Compact Flash adapter with Haiku. Linux uses the pata_pcmcia driver. Is there an expected Milestone for Cardbus support?

[stippi]

Sorry to disappoint you like this, but this is not how our development model works. Basically everyone works on what he finds most important. When we plan the next release, we may make certain features a requirement for the release to happen, so that the likelihood of someone working on it increases. I doubt it will be the case for this ticket, I'm afraid, but I may be wrong.

It's simply this: We have no one who is being paid to work on Haiku, therefor there is no one who can be told what to work on and in what timeframe.

[thetick]

Yes I know how open source software is developed. A few years back I worked on some commercial QA software for testing and performance monitoring on open source Linux drivers. I just would think with a few developers using Thinkpads the cardbus drivers would be part of R1?

I really liked BeOS and am very impressed with Haiku although it appears to be well over 10 years before the first Haiku release. I'm not in agreement with many of the Haiku developers dislike for Linux and its release often motto. Although different it reminds me of the BSD elite early in the Linux days.

Anyway I would consider helping with device driver development but I can't seem to ever get a good feeling when I open an issue. I guess I'll just use Linux for the next 10 years. BTW the ACPI (battery status/shutdown/reboot) on my Thinkpad is working pretty good almost making me want to work on the thermal module.

[stippi]

You should voice your opinion on the Haiku development list. I don't understand why you think it will take Haiku another 10 years before releasing R1. And I don't understand what you mean by "can't seem to ever get a good feeling when I open an issue". You mean you lack the feeling that the issue will be fixed at all? Please voice your concerns on the Haiku or Haiku-development list. This is not a good place.

[anevilyak]

Replying to thetick:

Yes I know how open source software is developed. A few years back I worked on some commercial QA software for testing and performance monitoring on open source Linux drivers. I just would think with a few developers using Thinkpads the cardbus drivers would be part of R1?

Speaking for myself only, I can safely say I haven't used the cardbus/pcmcia slot on my laptops in about 6 years since every use I ever had for them has since been supplanted by cheaper USB devices. So yes, even as a laptop user there isn't generally much motivation to work on this.

[thetick]

Sorry about the rant. I'll keep my comments brief. Just that Haiku is so very close to being useful. I did not make myself clear but I meant to say 10 years from openbe to an actual R1 release.

As for as my laptop an old Thinkpad A22m, I only have one 1.1 USB port so I would like to be able to use my compact flash from PCMCIA.

A PCcard driver would be beyond my time commitments, but I still might look into pata_pcmcia bridge or thermal module.