Quote:
ipw2200 module works with my 2915 on opensuse 10.3. I downloaded latest compat-wireless package and left Efika compiling it at nighttime (please do not denounce me for abuse!!!). I just gave it a try and it seems to work.
Good. Don't worry. I compile kernels on my Efika. It takes 10 hours from "make" to having a zImage.
Quote:
I suspect that there is some hotplug/firmware-helper issue with this, but as it is not SuSE related, this is almost off-topic. Never mind. Luckily, chameleon guys know how to tame the power(ful)pc beast.
Well, I would like to know what the real problem is here. It is probably a firmware problem. As for SuSE, ipw2200 is going to be in the 11.0 SuSE kernel (along with rt2x00, hooray!) since they all got mainlined with the stablization of the new 802.11 stack. If they don't work on PowerPC for some reason we can tell them not to build them to the kernel and save some time and space and effort ;)
Quote:
P.S. Is there a way to detect endianness problems in drivers (apart from diff)? I need to fix a quite old rt2x00 release.
The only way to tell is to know what data it expects, and see what data it gets - or know what data it wants, and cross reference the data you're giving it.
ipw2200 got a lot of "endian fixes" over the months and years, but who knows if they all got caught. I have never seen anyone mention that they got it working on anything but a Centrino laptop..
This code makes me shiver though;
Code:
3081 /* load new ipw uCode */
3082 for (i = 0; i < len / 2; i++)
3083 ipw_write_reg16(priv, IPW_BASEBAND_CONTROL_STORE,
3084 le16_to_cpu(image));
Why are they converting Little Endian microcode data to CPU endian format for loading into a ROM which the *device* needs? What bearing does the CPU endian format have here?