Comment 5 for bug 1077704
Revision history for this message
| Steve Payne (c-launchpad-iamsrp-com) wrote | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Just a quick update on this. First, I did a bit of digging and as far as I can tell the hardware should support connecting to ad-hoc networks (this was gleaned from peering at the chips in an hardware teardown of the devices and then reading up on the chip-set specs).
I then spent an evening trying to walk through the kernel source; attempting to follow the call tree to uncover where the EOPNOTSUPP was coming from. I, alas, ended up going around in circles so I might need to revisit this. (I did try putting in some debugging messages but didn't see anything when I flashed the new kernel to the device; so I either failed to add them as I thought or failed to correctly flash in the hacked kernel.)
Bottom line: I think that it should be possible to fix the kernel source to handle this but I haven't yet figured out quite how. I suck. Oh well...