AR5007, we know how to get it work, further progress needed!

[milan475]

Hi everybody,

 

Following this guide it is possible to get our AR5007 working.

But it is really annoying to start and close KisMAC every time we boot up our mac.

 

So I'm wondering what exactly happens when I start KisMAC. It seems like it loading of the drivers does the trick. Because after one has closed KisMAC airport is able to find networks by itself.

 

And now I wonder if it is probably KisMAC that gives power to the wificard. Like in windows happens when you press the wifi softswitch. If the softswitch is off, windows sees the card but it isn't able to detect networks. Same as in mac when you haven't started kismac yet.

 

This presuming only got bigger when i was digging in the souce of kismac and I saw this file: http://trac.kismac-ng.org/browser/trunk/So...ty/Apple80211.h with the following functions:

 

150

151 /*

152 * WirelessAttach()

153 *

154 * WirelessAttach should be called before all other Wireless functions.

155 *

156 * outContext returns the contextPtr you will pass

157 * to all other Wireless functions

158 * The second argument must be zero.

159 */

160 extern WIErr WirelessAttach(

161 WirelessContextPtr *outContext,

162 const UInt32);

163

164 /*

165 * WirelessDetach()

166 *

167 * WirelessDetach is called after you are done calling Wireless functions.

168 * It will free all memory being used by the library.

169 *

170 * inContext is the contextPtr you want to dispose of.

171 */

172 extern WIErr WirelessDetach(

173 WirelessContextPtr inContext);

174

175 /*

176 * WirelessGetPower()

177 *

178 * WirelessGetPower returns the power state of Airport.

179 *

180 * inContext is the contextPtr created by WirelessAttach.

181 * outPower is 0 for off and 1 for on.

182 */

183 extern WIErr WirelessGetPower(

184 WirelessContextPtr inContext,

185 UInt8 *outPower);

186

187 /*

188 * WirelessSetPower()

189 *

190 * WirelessSetPower will turn Airport on or off.

191 *

192 * inContext is the contextPtr created by WirelessAttach.

193 * inPower is 0 for off and 1 for on.

194 */

195 extern WIErr WirelessSetPower(

196 WirelessContextPtr inContext,

197 UInt8 inPower);

198

199 /*

200 * WirelessGetEnabled()

201 *

202 * WirelessGetEnabled could have returned the Enabled state of Airport,

203 * but it seems to rather return the Power state.

204 *

205 * inContext is the contextPtr created by WirelessAttach.

206 * outEnabled is 0 for off and 1 for on.

207 */

208 extern WIErr WirelessGetEnabled(

209 WirelessContextPtr inContext,

210 UInt8 *outEnabled);

211

212 /*

213 * WirelessSetEnabled()

214 *

215 * WirelessSetEnabled will enable or disable Airport communication.

216 *

217 * inContext is the contextPtr created by WirelessAttach.

218 * inEnabled is 0 for off and 1 for on.

219 */

220 extern WIErr WirelessSetEnabled(

221 WirelessContextPtr inContext,

222 UInt32 inEnabled);

223

224 /*

225 * WirelessGetInfo()

226 *

227 * WirelessGetInfo returns info about the state

228 * of the current wireless connection.

229 *

230 * inContext is the contextPtr created by WirelessAttach.

231 * outInfo is a WirelessInfo structure containing state info.

232 */

233 extern WIErr WirelessGetInfo(

234 WirelessContextPtr inContext,

235 WirelessInfo *outInfo);

 

it seems like these functions enable the wireless card.

 

What do you think? Am I right?

And is there anyone who knows how to deal with the file above?

 

I hope, together we will all be able to let our AR5007 chip work perfectely!!

 

Grtz,

Milan

 

A Compaq Presario CQ70 user and yes, I wrote this message using wifi in MAC

 

PS.

My English might not be totally correct, you've got to blame my dutch school for it