wirelessdriver-devel — Discussion of development related issues

[Wirelessdriver-devel] Trying to get SkyLine with PCI adapter to work

[Otto M. <ot...@dr...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I've been experimenting with getting my SkyLine 11Mbs with PCI adapter 
working with the wireless driver in my B&W PowerMac. So far, I've been 
able to get the card recognized by the kernel using the standard 10.1.4 
IOPCCardFamiliy driver. So that is good news. But starting the card 
either results in a mapping error, or in a kernel panic...

These are the steps I've done:

I've put an entry into the the Info.plist file of the IOPCCardFamily 
driver:

<key>PowerMac1,1</key>
<dict>
	<key>I/O Port Ranges</key>
	<array>
		<data>
			AAAAAAAAj/8=
		</data>
	     <data>
			AACgAAAA//8=
		</data>
	</array>
	<key>Memory Ranges</key>
	<array>
  		<data>
			hAAAAJ////8=
	 	</data>
	</array>
</dict>

(These values are based on an educated guess, see below)

Using this condfig, my SkyLine card gets recognized (there seems to be a 
type in the Info.plist of the WirelessDriver, it lists the/a Skyline 
card as having number HFA3843x, while my card report number HFA384x), 
see below for the ioreg listings. The problem is that initializing the 
card fails. Here are the system.log entries:

Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::probe(pccard156,2)
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::probe(pccard156,2)
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(pccard156,2) <1>
Apr 28 13:49:54 power-eth mach_kernel: Ethernet(BMac): Link up at 10 
Mbps - Half Duplex
Apr 28 13:49:54 power-eth mach_kernel: IOKernelDebugger: Debugger 
attached
Apr 28 13:49:54 power-eth mach_kernel: IOPCCard info:   
IOPCCard16Enabler::configure using index 0x01: Vcc 3.
3, irq 255, io 0x0000-0x003f
Apr 28 13:49:54 power-eth mach_kernel: Didn't make map 00000000 : 
00000040
Apr 28 13:49:54 power-eth mach_kernel: org_noncontiguous_WirelessDriver: 
Map Failed
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(provider=0x11da400, this=0x11d
e000) ** ABORTING! **
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(pccard156,2) <2> failed
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(pccard156,2) <1>
Apr 28 13:49:54 power-eth mach_kernel: IOPCCard info:   
IOPCCard16Enabler::configure using index 0x01: Vcc 3.
3, irq 255, io 0x0000-0x003f
Apr 28 13:49:54 power-eth mach_kernel: Didn't make map 00000000 : 
00000040
Apr 28 13:49:54 power-eth mach_kernel: org_noncontiguous_WirelessDriver: 
Map Failed
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(provider=0x11da400, this=0x11f
6000) ** ABORTING! **
Apr 28 13:49:54 power-eth mach_kernel: 
org_noncontiguous_WirelessDriver::start(pccard156,2) <2> failed

So it looks like the card cannot be mapped into memory. Since tha card 
is matched both by the edited HFA entry and the pccard156,2 entry, it 
gets two attempts, I guess. The irq (255) also looks suspicious to me.

Using LinuxPPC lspci -vv on the same machine (which works fine, after 
having edited the /etc/pcmcia/config.opts to extend the memory range to 
start from 0x80000000, instead of 0x90000000), I can see that the card 
gets mapped to address 0x80885000:


01:04.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus 
Controller (rev 01)
	Subsystem: SCM Microsystems: Unknown device 3000
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
	Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 16, cache line size 08
	Interrupt: pin A routed to IRQ 25
	Region 0: Memory at 80885000 (32-bit, non-prefetchable) [size=4K]
	Bus: primary=80, secondary=1c, subordinate=00, sec-latency=176
	I/O window 0: 00000000-00000003
	I/O window 1: 00000000-00000003
	BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset+ 16bInt- PostWrite+
	16-bit legacy interface ports at 0001

And here's the cardtl ident output:

Socket 0:
   product info: "INTERSIL", "HFA384x/IEEE", "Version 01.02", ""
   manfid: 0x0156, 0x0002
   function: 6 (network)

If I adapt the memory region in Info.plist of the IOPCCardFamily driver 
to start with address 0x80000000 (value gAAAAJ////8=), I get a kernel 
panic in the IOPCCardFamily driver. With different values for the mem 
range (copied from other entries in the sme file) I also saw panics in 
the WirelessDriver, being called from the IOPCCardFamily driver.

Do you have any suggestions or hints? Like anwers to the questions:

- - What should be the memory range of the in the Info.plist of the 
PowerMac1,1 entry in the IOPCCardFamily driver?
- - What should be the Info.plist values of the SkyLine 11mbs card? Has 
the HFA entry a typo or not?
- - Is the interrupt value of 255 indeed wrong?
- - What debugging strategy should I use?


Thanks in advance, Otto

Below are the ioreg -l listings:

     |     |   | +-o IOPCCardBridge  <class IOPCCardBridge>
     |     |   |   | {
     |     |   |   |   "Bridge IO Ranges" = (0,36863,40960,65535)
     |     |   |   |   "IOPersonalityName" = "IOPCCardFamily"
     |     |   |   |   "Configuration Settings" = {"PowerBook"={"Memory 
Ranges"=(<90000000afffffff>),"I/O Port 
Ranges"=(<fe000000fe00ffff>)},"PowerBook1,1"={"Memory 
Ranges"=(<900000009fffffff>),"I/O Port 
Ranges"=(<fe000000fe00ffff>)},"PowerBook3,4"={"Memory 
Ranges"=(<900000009fffffff>),"I/O Port 
Ranges"=(<f2000000f2008fff>,<f200a000f200ffff>)},"PowerBook3,1"={"Memory 
Ranges"=(<900000009fffffff>),"I/O Port 
Ranges"=(<f2000000f2000fff>,<f2002000f200ffff>)},"PowerBook3,2"={"
Memory Ranges"=(<900000009fffffff>),"I/O Port 
Ranges"=(<f2000000f2008fff>,<f200a000f200ffff>)},"PowerBook3,3"={"Memory 
Ranges"=(<900000009fffffff>),"I/O Port
Ranges"=(<f2000000f2008fff>,<f200a000f200ffff>)},"PowerMac1,1"={"Memory 
Ranges"=(<840000009fffffff>),"I/O Port 
Ranges"=(<0000000000008fff>,<0000a0000000ffff>)
},"X86PC"={"Memory 
Ranges"=(<000c0000000fffff>,<a0000000a0ffffff>,<6000000060ffffff>),"I/O 
Port Ranges"=(<00000100000004ff>,<00000800000008ff>,<00000c0000000cff>)}}
     |     |   |   |   "Debug Settings" = {"Card Services"=3,"Card 
Bus"=3,"Driver Services"=4,"i82365"=2}
     |     |   |   |   "Bridge Memory Ranges" = (-2080374784,-1610612737)
     |     |   |   |   "IOProviderClass" = "IOPCIDevice"
     |     |   |   |   "CFBundleIdentifier" = 
"com.apple.iokit.IOPCCardFamily"
     |     |   |   |   "Power Management private data" = "{ this object = 
01127600, interested driver = 01127600, driverDesire = 2, deviceDesire = 
0, ourDesire
dPowerState = 2, previousRequest = 2 }"
     |     |   |   |   "IOKitDebug" = 0
     |     |   |   |   "IOMatchCategory" = "IODefaultMatchCategory"
     |     |   |   |   "IOPCIClassMatch" = "0x06070000"
     |     |   |   |   "Power Management protected data" = "
{ theNumberOfPowerStates = 3, version 1, power state 0 = 
{ capabilityFlags 00000000, outputPowerCha
racter 00000000, inputPowerRequirement 00000000, staticPower 0, 
unbudgetedPower 0, powerToAttain 0, timeToAttain 0, settleUpTime 0, 
timeToLower 0, settleDownT
ime 0, powerDomainBudget 0 }, power state 1 = { capabilityFlags 
00000000, outputPowerCharacter 00000400, inputPowerRequirement 00000400, 
staticPower 0, unbudg
etedPower 0, powerToAttain 0, timeToAttain 0, settleUpTime 0, 
timeToLower 0, settleDownTime 0, powerDomainBudget 0 }, power state 2 = 
{ capabilityFlags 000000
02, outputPowerCharacter 00000002, inputPowerRequirement 00000002, 
staticPower 0, unbudgetedPower 0, powerToAttain 0, timeToAttain 0, 
settleUpTime 0, timeToLo
wer 0, settleDownTime 0, powerDomainBudget 0 }, aggressiveness = 0, 
myCurrentState = 2, parentsCurrentPowerFlags = 00000002, maxCapability = 
2 }"
     |     |   |   |   "IOClass" = "IOPCCardBridge"
     |     |   |   |   "IOProbeScore" = -100
     |     |   |   |   "ParentKey" = 
"KEXTBundle?com.apple.iokit.IOPCCardFamily"
     |     |   |   | }
     |     |   |   |
     |     |   |   +-o pccard156,2@0,0  <class IOPCCard16Device>
     |     |   |       {
     |     |   |         "VersionOneInfo" = 
("INTERSIL","HFA384x/IEEE","Version 01.02","")
     |     |   |         "VendorID" = 342
     |     |   |         "DeviceID" = 2
     |     |   |         "IOInterruptSpecifiers" = (<00000000>)
     |     |   |         "Power Management private data" = "{ this 
object = 011ebf00, interested driver = 011ebf00, driverDesire = 0, 
deviceDesire = 0, ourDesi
redPowerState = 2, previousRequest = 2 }"
     |     |   |         "IODeviceMemory" = ("IOGeneralMemoryDescriptor 
is not serializable")
     |     |   |         "FunctionExtension" = 
(<0107>,<0240420f00>,<0280841e00>,<0260ec5300>,<02c0d8a700>,<0307>,<04060000c5099172>
,<0501>)
     |     |   |         "Power Management protected data" = "
{ theNumberOfPowerStates = 3, version 1, power state 0 = 
{ capabilityFlags 00000000, outputPowerC
haracter 00000000, inputPowerRequirement 00000000, staticPower 0, 
unbudgetedPower 0, powerToAttain 0, timeToAttain 0, settleUpTime 0, 
timeToLower 0, settleDow
nTime 0, powerDomainBudget 0 }, power state 1 = { capabilityFlags 
00000000, outputPowerCharacter 00000400, inputPowerRequirement 00000400, 
staticPower 0, unbu
dgetedPower 0, powerToAttain 0, timeToAttain 0, settleUpTime 0, 
timeToLower 0, settleDownTime 0, powerDomainBudget 0 }, power state 2 = 
{ capabilityFlags 0000
0000, outputPowerCharacter 00000002, inputPowerRequirement 00000002, 
staticPower 0, unbudgetedPower 0, powerToAttain 0, timeToAttain 0, 
settleUpTime 0, timeTo
Lower 0, settleDownTime 0, powerDomainBudget 0 }, aggressiveness = 0, 
myCurrentState = 2, parentsCurrentPowerFlags = 00000002, maxCapability = 
2 }"
     |     |   |         "FunctionName" = "Network Adapter"
     |     |   |         "FunctionNumber" = 0
     |     |   |         "IOInterruptControllers" = 
("IOPCCardInterruptController00010400")
     |     |   |         "FunctionID" = 6
     |     |   |         "SocketNumber" = 0
     |     |   |         "IOName" = "pccard156,2"
     |     |   |       }


- --
Otto Moerbeek       ot...@dr...
Public Key fingerprint: 13F7 EB00 14D7 7810 88DA  CDDE DBF1 B5AB 2FB7 
A5A3

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (Darwin)
Comment: For info see http://www.gnupg.org

iD8DBQE8zjzI2/G1qy+3paMRAiwFAKCKYkImt+aXlDxPRVk0AQFEi6AD+wCgsGAm
Q1a6y3DZ95LG4EqqHHy+r8I=
=MoEo
-----END PGP SIGNATURE-----

Re: [Wirelessdriver-devel] Switching to new Project builder?

[Rob M. <ro...@ma...>]

I've already made the change.  I like the new project builder, 
but GCC3 can't be used for kexts yet - best to wait for Jaguar 
for that one.

-Rob

On Wednesday, April 24, 2002, at 11:04 AM, David Ross wrote:

> Hello -
>
> Apple released recently a new beta version of project builder 
> and gcc, should we migrate now or later to these new tools?
>
> -- Dave
>
>
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel

Re: [Wirelessdriver-devel] 10.1.4 update problematic?

[Jim R. <ji...@ro...>]

Does anyone else have experience with the driver under 10.1.4?

I need to upgrade to build and run Chimera but I can't do that if my 
WiFi card won't work.

Thanks,

Jim

On Thursday, April 18, 2002, at 01:34  PM, Wolfgang Fischer wrote:

>
> Hello,
>
> since I updated to 10.1.4 I have strange problems. I am used to put the 
> PB to sleep and wake it up at a new location. I change the 
> Network-profile and the network name in the wireless prefs, and 
> continue my work. Even Mail.app eventually learns, which servers are 
> reachable and which not. M$-Exploder is a little slow updating its  
> proxy configuration, but since I use mozilla anyway, thats not a 
> problem.
> But this does not longer work for me, the PB does not get a connection 
> to the network, mail hangs unkillable, I cannot start new applications, 
> like terminal to run ifconfig et.al. All new started applications 
> bounce for a while, do not start and stop bouncing. They do not show up 
> in the "kill immediate"-apple-menu-entry.
> A more or less hard reboot is necessary to get the PB back to the net. 
> I have a SMC card and everything worked quite nice until the update. 
> Next time when I switch networks I keep a terminal open to get better 
> debugging information.
>
> Has anyone else problems like this since updating?
>
> Wolfgang

[Wirelessdriver-devel] Switching to new Project builder?

[David R. <db...@cs...>]

Hello -

Apple released recently a new beta version of project builder and gcc, 
should we migrate now or later to these new tools?

-- Dave

[Wirelessdriver-devel] 10.1.4 update problematic?

[Wolfgang F. <wf...@wf...>]

Hello,

since I updated to 10.1.4 I have strange problems. I am used to put the 
PB to sleep and wake it up at a new location. I change the 
Network-profile and the network name in the wireless prefs, and continue 
my work. Even Mail.app eventually learns, which servers are reachable 
and which not. M$-Exploder is a little slow updating its  proxy 
configuration, but since I use mozilla anyway, thats not a problem.
But this does not longer work for me, the PB does not get a connection 
to the network, mail hangs unkillable, I cannot start new applications, 
like terminal to run ifconfig et.al. All new started applications bounce 
for a while, do not start and stop bouncing. They do not show up in the 
"kill immediate"-apple-menu-entry.
A more or less hard reboot is necessary to get the PB back to the net. I 
have a SMC card and everything worked quite nice until the update. Next 
time when I switch networks I keep a terminal open to get better 
debugging information.

Has anyone else problems like this since updating?

Wolfgang

[Wirelessdriver-devel] Update to the CVS source

[David R. <n1...@ma...>]

Hello -

I've just committed changes to the pref pane that should do the 
following:

IF you change the text in the network name, the WEP key field should 
blank
IF you apply a network name with a blank WEP key, it should look up and 
insert the key from the KeyChain.

I am asking for people to test this, as I left my card 2 hrs away and I 
can't.

Next up:
1) Adding a signal to noise graph
2) Adding a startup item

-- Dave

[Wirelessdriver-devel] Re: New b4 installer available for testing

[Rob M. <ro...@ma...>]

I've stuck a disk image up on my iDisk that has essentially the 
same thing in it as a disk image.  The installers are packaged a 
little differently, but the installed code should be the same.

The message that Matthew Liao-Troth sent earlier saying that the 
preference pane isn't showing up even though it's present got me 
curious... I'm now having the same issue with this installer on 
mine.  Is there anyone out there who might be a little less 
tired than I that is able to spot what I've got buggered up in 
the prefPane install?

My iDisk:  <http://homepage.mac.com/robm>

-Rob


On Friday, March 29, 2002, at 07:26 PM, yuriwho wrote:

> I have posted a pre-release of WirelessDriver_b4.sit for testing on my
> iTools homepage. This version is for testing by list members 
> before official
> public release. It is equivalent to the latest version in CVS of the
> existing driver code (it is not Robs new re-write of the 
> codebase..you will
> have to wait a little longer for that). The new version 
> includes support for
> additional cards (let us know if your card is not supported, or 
> supported
> but not listed in the FAQ), ability to enter ascii WEP keys and 
> have them
> converted directly to hex (this does NOT work with Apples 
> basestations..see
> the FAQ), the selection of channels for WEP keys (useful for 
> some 3rd party
> basestations) and several bug fixes...no more crashing system 
> preferences if
> the card was not recognized by the driver. The FAQ that comes 
> with the new
> release is more up-to-date than the version on the website. 
> They will come
> into sync when we release.
>
> The driver can be found at:
>
> http://homepage.mac.com/yuriwho
>
> called:
>
> WirelessDriver_b4.sit
>
> Please test this new version and report problems to the me or 
> the forum. We
> hope to make a public release soon. Please, let me know there are any
> unusual problems with this installer.
>
> Cheers,
>
> Y
> --
> yu...@ma...
> WirelessDriver Project Manager
>
> Please read the FAQ at http://wirelessdriver.sourceforge.org/faq.html
> It has probably been updated since the last time you looked at it.
>

Re: [Wirelessdriver-devel] Announce: 1st CVS commit of rewritten source base

[h1kari <h1...@da...>]

Rob,

I've finally found out how to do the ioctl stuff with IONetworkInterface and
I'm in the middle of working on some modifications with WirelessDriver to
add support for bsd-airtools. I've made a bunch of modifications to the
driver and there aren't any compilation problems that I can find, but when
the kernel tries to load the modified driver when I insert the card, it is
unable to load it. I was wondering if you could provide me with any tips or
shortcuts on debugging what might be causing this problem, and if there's
any new source that I should work with, since it seems you're in the middle
of doing a lot of work on the project.

Also, I want to know how people feel about incorporating wicontrol/wiconfig
into the distribution, that uses the standard ioctl interface for card
configuration (I will need to at least partially port this over for basic
bsd-airtools support). Any thoughts?

Any help/insight is much appreciated.

Thanks,
-h1kari


-- 
David Hulton <h1...@da...>
Senior Researcher, Dachb0den Labs
http://www.dachb0den.com


On 1/20/02 2:45 PM, "Rob McKeever" <ro...@ma...> wrote:

> At long last...
> 
> I've checked in the source base I've been working on for far too
> long now.  It's not totally complete, but should be a good start
> for anyone looking to work on the driver side of things.  It
> should also fix some of the stability issues that have plagued
> the last code base (in other words, I can't crash this one).
> 
> This is a complete rewrite of what was there before.  It still
> lacks transmit and receive capability and WEP hasn't been added
> yet, but it's much cleaner and much, much more Darwin-like.
> 
> The project has been divided into a few different sections:
> WirelessController
> WirelessInterface
> ... not much done here yet, but this is where 802.11
> packet handling should reside
> 
> IntersilDriver
> ... core functionality for working with Intersil and
> Lucent/Orinoco PRISM chips
> 
> IntersilPCCard
> ... remaining functionality needed for PC Cards
> 
> UserClient
> WirelessUserClient
> ... designed to compile into a framework to ease the
> creation of user clients.
> 
> There's also a simple application in there to try and test the
> UserClient bits I've done.  For some reason, though, the
> UserClient isn't connecting properly.  I'll look into it, but
> I've got a few other things that take precedence.  If somebody
> wants to beat me to it, please feel free.
> 
> 
> Enjoy!
> 
> -Rob
> 
> 
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
> 

[Wirelessdriver-devel] New b4 installer available for testing

[yuriwho <yu...@ma...>]

I have posted a pre-release of WirelessDriver_b4.sit for testing on my
iTools homepage. This version is for testing by list members before official
public release. It is equivalent to the latest version in CVS of the
existing driver code (it is not Robs new re-write of the codebase..you will
have to wait a little longer for that). The new version includes support for
additional cards (let us know if your card is not supported, or supported
but not listed in the FAQ), ability to enter ascii WEP keys and have them
converted directly to hex (this does NOT work with Apples basestations..see
the FAQ), the selection of channels for WEP keys (useful for some 3rd party
basestations) and several bug fixes...no more crashing system preferences if
the card was not recognized by the driver. The FAQ that comes with the new
release is more up-to-date than the version on the website. They will come
into sync when we release.

The driver can be found at:

http://homepage.mac.com/yuriwho

called:

WirelessDriver_b4.sit

Please test this new version and report problems to the me or the forum. We
hope to make a public release soon. Please, let me know there are any
unusual problems with this installer.

Cheers,

Y
-- 
yu...@ma...
WirelessDriver Project Manager

Please read the FAQ at http://wirelessdriver.sourceforge.org/faq.html
It has probably been updated since the last time you looked at it.

[Wirelessdriver-devel] Updated Command line Tool in CVS

[David R. <db...@cs...>]

I just committed an updated version of the command line tool.

Here is what is changed:
* Fixed bugs in WirelessConfig command line tool. It will now display 
the help message without having a bus error.
* Added sanity checking so that if a user enters an invalid set of 
switches the tool will catch it and display the help message.

-- Dave

Re: [Wirelessdriver-devel] Farallon SkyLINE 2 Mbps Wireless

[Rob M. <ro...@ma...>]

The new codebase might actually work with it.  I'm writing that 
to work as close to the device specification documents that it 
should.

Of course, without one to test and play with, it's hard to 
guarantee anything.  If any out there wants to try and put a bit 
of pressure on Farallon/Proxim to provide us with a few samples, 
it can't hurt...

-Rob


On Monday, January 28, 2002, at 05:06 AM, Edwards, Lawrence wrote:

> Guys,
> When do you think the driver will include support for the 
> Farallon SkyLINE 2
> Mbps Wireless card? Will it ever be included - I suppose it's a 
> pretty old
> card nowadays.
> Lawrence
>
>
>
>
> Lawrence Edwards
> BFT  -  Beauchamp Financial Technology Ltd
> 30 Cannon Street        London       EC4M  6YN
> Tel:      020 7653 5859         Fax:    020 7653 5851
> Mobile: 07905 208315        email:  led...@bf...
> WWW: http://www.bftl.com
>
>
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel

[Wirelessdriver-devel] Farallon SkyLINE 2 Mbps Wireless

[Edwards, L. <LEd...@BF...>]

Guys,
When do you think the driver will include support for the Farallon SkyLINE 2
Mbps Wireless card? Will it ever be included - I suppose it's a pretty old
card nowadays.
Lawrence




Lawrence Edwards
BFT  -  Beauchamp Financial Technology Ltd
30 Cannon Street        London       EC4M  6YN
Tel:      020 7653 5859         Fax:    020 7653 5851
Mobile: 07905 208315        email:  led...@bf...
WWW: http://www.bftl.com

[Wirelessdriver-devel] Fwd: Wireless networking support under OS X

[Rob M. <ro...@ma...>]

Just to make sure that everyone knows...

I just sent the following e-mail off to a contact at Asante.  It 
seems that someone has "developed" a driver for them that is 
simply a copy of our Beta 3 driver minus the preference pane and 
using a custom installer.

-Rob



Begin forwarded message:

> From: Rob McKeever <ro...@ma...>
> Date: Wed Jan 23, 2002  05:42:11 PM America/Vancouver
> To: bmu...@as...
> Subject: Wireless networking support under OS X
>
> I wanted to say that it was good to meet you at MacExpo.  In 
> case you don't remember, I was the fellow who has written the 
> open source driver that works with your wireless networking 
> 802.11b PC Card and we discussed the possibility of getting one 
> or two of your cards to use as samples or testing purposes.  At 
> the time, you also mentioned that Asante had just published 
> it's own drivers for this card.
>
> Unfortunately, due in part to an overabundance of work since 
> returning from the expo and due to your driver updates site 
> being down every time I checked until now, I hadn't had a 
> chance to take a look at your rivers.  Now that I have, I 
> thought I should make the following known to you and your 
> company:
>
> 	The driver Asante is distributing as for it's AL1011 PC 
> Card is the same driver that was developed by myself and others 
> as part of an open source project.
>
> I don't know who is taking credit for this driver internally at 
> Asante, but I would like to make sure that you know that this 
> is the same driver being distributed by us from 
> <http://wirelessdriver.sourceforge.net> as Beta 3 of our 
> driver.  The differences being that, in your version, you are 
> not distributing the preference pane that David Ross wrote as 
> part of the project and you are using a customized installer.
>
> Please note:  while we did this as an open source project, it 
> is covered by certain licensing terms that I will attach to the 
> end of this message.  By distributing your installer in the 
> form that you are, without any credits or a copy copyrights as 
> required by the BSD license we use, you are in violation of the 
> licensing terms.  We would like to see this corrected as soon 
> as possible and hope that this can be done without resorting to 
> further action being required.
>
> We would be happy to work with you to see the completion of a 
> driver for your product.  We recognize the need and, being the 
> people who did this port in the first place, feel that we would 
> be an excellent choice for completing this for you.  I have 
> recently rewritten the driver from scratch in an effort to 
> clear up many issues that have been present and see that this 
> could also be used either as a completed driver for your 
> product or as a starting point towards a customized version 
> developed in conjuction with you specifically for your 
> product.  As a start towards developing a relationship of this 
> sort, I invite you to check out our website and the current 
> state of the wirelessdriver project and would like to ask for 
> at least one card to be used as a sample for testing 
> compatibility with our code.
>
> Thank you,
>
> Rob McKeever
> ro...@ma...
>
>
>
> As promised, a copy of the terms under which our driver code 
> was provided publicly.  This disclaimer is stated prominently 
> at the beginning of each source file and during the 
> installation process when using our installer:
>
> /*
>  * Copyright (c) 2001
>  *	Benjamin Herrenschmidt	<be...@mi...>
>  *	Louis Gerbarg		<ge...@cs...>
>  *	Rob McKeever		<ro...@ma...>
>  *	All rights reserved.
>  *
>  * Redistribution and use in source and binary forms, with or without
>  * modification, are permitted provided that the following conditions
>  * are met:
>  * 1. Redistributions of source code must retain the above copyright
>  *    notice, this list of conditions and the following disclaimer.
>  * 2. Redistributions in binary form must reproduce the above copyright
>  *    notice, this list of conditions and the following 
> disclaimer in the
>  *    documentation and/or other materials provided with the 
> distribution.
>  * 3. All advertising materials mentioning features or use of 
> this software
>  *    must display the following acknowledgement:
>  *	This product includes software developed by Benjamin Herrenschmidt,
>  *	Louis Gerbarg and Rob McKeever.
>  * 4. Neither the name of the authors nor the names of any 
> co-contributors
>  *    may be used to endorse or promote products derived from 
> this software
>  *    without specific prior written permission.
>  *
>  * THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
>  * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
>  * LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND 
> FITNESS FOR
>  * A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE 
> COPYRIGHT
>  * HOLDERS OR THE VOICES IN THEIR HEADS BE LIABLE FOR ANY 
> DIRECT, INDIRECT,
>  * INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
>  * BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
> SERVICES; LOSS
>  * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 
> CAUSED AND
>  * ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 
> LIABILITY, OR
>  * TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 
> OUT OF THE
>  * USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 
> SUCH DAMAGE.
>  */
>

[Wirelessdriver-devel] Announce: 1st CVS commit of rewritten source base

[Rob M. <ro...@ma...>]

At long last...

I've checked in the source base I've been working on for far too 
long now.  It's not totally complete, but should be a good start 
for anyone looking to work on the driver side of things.  It 
should also fix some of the stability issues that have plagued 
the last code base (in other words, I can't crash this one).

This is a complete rewrite of what was there before.  It still 
lacks transmit and receive capability and WEP hasn't been added 
yet, but it's much cleaner and much, much more Darwin-like.

The project has been divided into a few different sections:
	WirelessController
	WirelessInterface
		... not much done here yet, but this is where 802.11 
packet handling should reside

	IntersilDriver
		... core functionality for working with Intersil and 
Lucent/Orinoco PRISM chips

	IntersilPCCard
		... remaining functionality needed for PC Cards

	UserClient
	WirelessUserClient
		... designed to compile into a framework to ease the 
creation of user clients.

There's also a simple application in there to try and test the 
UserClient bits I've done.  For some reason, though, the 
UserClient isn't connecting properly.  I'll look into it, but 
I've got a few other things that take precedence.  If somebody 
wants to beat me to it, please feel free.


Enjoy!

-Rob

[Wirelessdriver-devel] Command line tool is here

[David R. <n1...@ma...>]

Hello -

I've just committed the sources for command line tool, It seems to work 
pretty well. I'll be adding in an option in the preference pane to make 
a startup item that will configure your card as part of the boot 
process. Ie no more need for the preference pane to load on login and 
system-wide wireless network stats.

Give it a try and tell me if there is anything missing that you would 
like.

-- Dave

[Wirelessdriver-devel] Update to the GUI

[David R. <n1...@ma...>]

In the CVS there is a new version of the GUI, fixes and improvements are 
as follows:
* Fixed a crashing bug where if you were to hit apply more than twice 
the System Preference's app would crash
* Changed the layout of the pane to make it easier to see what options 
are grouped together
* Changed the checkbox to a popup menu for changing the format of the 
inputed WEP key

Comments are appreciated.

-- Dave

[Wirelessdriver-devel] FAQ updated

[yuriwho <yu...@ma...>]

I have updated the FAQ to make it a more current. Let me know if 
anything else should be changed/added.

Y

Re: [Wirelessdriver-devel] Updated wireless config panel needs some testing

[Michael E. <mre...@ho...>]

I havn't loaded the new panel yet, however, I do have a question reguarding 
the old panel (but new enough to use the keychain).

Both myself and my fiance use this laptop.  Of course, I like her to log in 
as herself.  What I'm noticing is that when I am logged in, the keys work 
and I can auth with the AP without problems.

When she logs in, especially if she is first after boot, it doesn't appear 
that she can set the key.  If you put it in, it just doesn't seem to work.

Are there access rights issues with the pannel when using a 
non-administrator?  I'm assuming that there are ioctl's that are needed in 
order to actually set the key - is this something that normal users don't 
have access to?

Thanks!

Mike



>From: David Ross <n1...@ma...>
>To: wir...@li...
>Subject: [Wirelessdriver-devel] Updated wireless config panel needs some 
>testing
>Date: Fri, 11 Jan 2002 11:08:08 -0500
>
>Hello -
>
>In the CVS tree there is an option to allow one to enter their WEP key
>as a literal string. I have tested it somewhat and it seems to work. I
>am hoping others can confirm this. Also if the new feature is unclear I
>would like feed back on how to make it sensical.
>
>Thanks
>-- Dave
>
>
>_______________________________________________
>Wirelessdriver-devel mailing list
>Wir...@li...
>https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

[Wirelessdriver-devel] Updated wireless config panel needs some testing

[David R. <n1...@ma...>]

Hello -

In the CVS tree there is an option to allow one to enter their WEP key 
as a literal string. I have tested it somewhat and it seems to work. I 
am hoping others can confirm this. Also if the new feature is unclear I 
would like feed back on how to make it sensical.

Thanks
-- Dave

[Wirelessdriver-devel] Two things - update to the gui, and feedback on new version of Kext

[David R. <n1...@ma...>]

Hi -

I've uploaded an update to the gui that allows you to enter in the WEP 
key as a literal string. I've done some preliminary tests that show that 
it will work, though if you use extended characters for your literal 
string and use it multiple times, system preferences will crash.

Secondly, the new kext still gives a kernel panic when the card is 
reinserted, though that may be because I'm using it on my new machine 
(g4 powerbook).

Cheers

-- Dave

[Wirelessdriver-devel] Improvements to the GUI

[David R. <n1...@ma...>]

Hi -

Did anyone try the improvements I rolled into the CVS a while back to 
the gui? Is it working for everyone? If there are any problems I'd like 
to know so I can fix them.

Thanks

-- Dave

[Wirelessdriver-devel] CVS update...

[Rob M. <ro...@ma...>]

OK...

This isn't the much larger code reorganization that I've got in 
the works, but I rolled some of the changes into the existing 
code to keep people a little bit happier.

** Card removal and reinsertion now works!  In it's current 
form, it still leaks memory every time it's removed, but it 
works.  (I've already fixed the memory leak in the other code 
base I've got in the works)

** For those out there running Wallstreet PowerBooks, the 
Top-of-Tree sources for IOPCCardFamily in the Darwin archives 
fixes some problems with the bottom card slot.  It might be 
worth your while to check it out (standard warnings and 
disclaimers should apply - as with any pre-release software).

If a few people out there can verify these fixes work as wel as 
they do for me, I'll get out an update tonight.


I hope to have a few more goodies before I head off to MacExpo.  
If anyone else here is heading down and wants to get together, 
drop me an e-mail and we'll sort out the details.

-Rob McKeever
ro...@ma...

Re: [Wirelessdriver-devel] status on driver and such

[h1kari <h1...@da...>]

I'm out of town, but I'll get you some registry dumps for my cards when I
get back to the office. Also, I was wondering if anyone on the list has
worked on implementing ioctl handlers for the drivers yet. I've briefly
tried messing with it, but to no avail.. For some reason the
IONetworkingFamily really likes to keep calling it's internal functions
instead of inheriting the ioctl functions (performCommand,
performGatedCommand, etc) in my derived function. I don't have much
experience with c++, so I might be doing something wrong.. Anyway, let me
know if you have done this, or are planning on doing this in the future (so
I can implement my airtools and generic wi config apps). Otherwise I'll keep
on digging and see if I can get it in. Also, what will the next significant
driver release include?

Thanks, and Happy Holidays !
-h1kari

On 12/22/01 8:33 AM, "Rob McKeever" <ro...@ma...> wrote:
> Seasons Greeting!
> 
> OK...
> 
> As many of us have discovered, the current driver works about as
> well under 10.1.2 as it did on earlier versions of OS X.  It's
> still got it's quirks - the are new and some have changed or
> gone away.
> 
> There is a new version in the works that aims to support the
> different cards much better.  I've been bogged down more with
> the day job recently than expected (I hate trade show
> deadlines), but it will be out soon (over the holidays).
> 
> What I need from everybody out there
> 1) A list of the IORegistry property strings for each card.
> Since the new driver will split support for the various
> cards up making it easier to handle all of the differences, I
> need to know what the various matching strings are out there to
> match card to driver.
> 2) A list of what is currently working/not working for each card type.
> This will help to sort out which chips/chipsets are
> actually in each card.
> 
> I've got the card databases from FreeBSD, linux and a few other
> sources and I'll use them for most of the info.  I'd like to
> make sure we get as detailed as possible to make this as good as
> possible.
> 
> 
> In any event... Seasons Greetings, Merry Christmas, Happy Yule,
> and all of the other greetings that I can never remember how to
> spell.
> 
> -Rob McKeever
> ro...@ma...
> 
> 
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
> 

[Wirelessdriver-devel] Update to the Preference Pane

[David R. <n1...@ma...>]

Hi all-

Happy Holidays. I've just committed into CVS an update to the preference 
pane giving KeyChain Support. Here are the caveats:
1) The passwords are stored upon apply
2) When you wish to look up a password tab out of the network name field 
and if there is a stored password it will be filled into the wep key 
field
3) Once a password is stored, it must be deleted in the keychain manager 
application since I can't get the keychain to allow me to update 
existing items.

Enjoy,

-- Dave

[Wirelessdriver-devel] status on driver and such

[Rob M. <ro...@ma...>]

Seasons Greeting!

OK...

As many of us have discovered, the current driver works about as 
well under 10.1.2 as it did on earlier versions of OS X.  It's 
still got it's quirks - the are new and some have changed or 
gone away.

There is a new version in the works that aims to support the 
different cards much better.  I've been bogged down more with 
the day job recently than expected (I hate trade show 
deadlines), but it will be out soon (over the holidays).

What I need from everybody out there
	1) A list of the IORegistry property strings for each card.
		Since the new driver will split support for the various 
cards up making it easier to handle all of the differences, I 
need to know what the various matching strings are out there to 
match card to driver.
	2) A list of what is currently working/not working for each card type.
		This will help to sort out which chips/chipsets are 
actually in each card.

I've got the card databases from FreeBSD, linux and a few other 
sources and I'll use them for most of the info.  I'd like to 
make sure we get as detailed as possible to make this as good as 
possible.


In any event... Seasons Greetings, Merry Christmas, Happy Yule, 
and all of the other greetings that I can never remember how to 
spell.

-Rob McKeever
ro...@ma...