Menu
▾
▴
wirelessdriver-devel — Discussion of development related issues
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(14) |
Nov
(16) |
Dec
(14) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
(6) |
May
(5) |
Jun
(3) |
Jul
(4) |
Aug
(3) |
Sep
|
Oct
(1) |
Nov
|
Dec
(1) |
| 2003 |
Jan
(4) |
Feb
(6) |
Mar
(1) |
Apr
|
May
(3) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(9) |
Dec
(4) |
| 2004 |
Jan
|
Feb
(2) |
Mar
|
Apr
(1) |
May
|
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
(3) |
Jul
(1) |
Aug
(5) |
Sep
(3) |
Oct
(1) |
Nov
|
Dec
|
|
From: Java N. <jav...@ho...> - 2004-04-26 13:32:51
|
Has anyone built the driver under Panther with xCode? What are the specific steps? Has the latest source code made it into CVS yet (with the improved WEP support, etc)? Thanks in advance. _________________________________________________________________ Lose those love handles! MSN Fitness shows you two moves to slim your waist. http://fitness.msn.com/articles/feeds/article.aspx?dept=exercise&article=et_pv_030104_lovehandles |
|
From: Klaus A. <kl...@fa...> - 2004-02-15 17:01:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I did a CVS co of the driver and wanted to compile it in panther, but=20 it seems like i have som problems compiling the WirelessConfig target=20 (I am really new to Xcode developer tools, so I have some problems=20 finding out exactly why it won't compile). I have two questions for the list: 1) is anything happening in CVS that is really nice to have ? I miss=20 network browsing and printing over appletalk quite a lot. I also have=20 big problems getting kismac to work with my dlink card - I was hoping=20 some of these issues would be solved in a CVS build of the driver .. 2) is it at all possible to build the driver in panther ? has anyone=20 tried ? Thanks in advance for any help :) - --- Med venlig hilsen Klaus Agnoletti System Tekniker Se vores nye Typo3 CMS baserede website p=E5 www.fab-it.dk ____________________________________________ Fab:IT ApS Telefon: 333 111 17 Vesterbrogade 50 D=F8gnvagt: 333 134 40 1620 K=F8benhavn V Telefax: 333 136 40 www.fab-it.dk kl...@fa... -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFAL6UuqwtbkvazLakRAsaqAJ0Zh9rxLuYnP/xGzKZKKTNbM1tHDACghFcl 87IjrO6jI/VEcGzlUiwmxGE=3D =3DIRlU -----END PGP SIGNATURE----- |
|
From: Java N. <jav...@ho...> - 2004-02-09 01:36:55
|
Hi Rob, I am curious when you might release this, or if you have a stable version you can share that is more recent than the December 4 version you last shared? Thanks in advance. >Still the latest released ones. I plan on doing another release around >MacWorld Expo. > >Any questions or comments? I know there were a few bugs that I've since >fixed in the current code that should make it into the next release. > >-Rob _________________________________________________________________ Plan your next US getaway to one of the super destinations here. http://special.msn.com/local/hotdestinations.armx |
|
From: Java N. <jav...@ho...> - 2003-12-28 01:44:03
|
I am wondering, does anyone have support digests before #474 and/or devel digests before #64 that you could share with me, as I just recently subscribed to these lists? I have been noticing that the archives of the list at sourceforge have dropped a few messages, and I find digests easier to handle. Thanks in advance for any assistance. _________________________________________________________________ Take advantage of our limited-time introductory offer for dial-up Internet access. http://join.msn.com/?page=dept/dialup |
|
From: Java N. <jav...@ho...> - 2003-12-06 16:38:01
|
Does the new code base fix the bug related to removal and reinsertion of cards that crashes the system? Thanks. _________________________________________________________________ Get holiday tips for festive fun. http://special.msn.com/network/happyholidays.armx |
|
From: Rob M. <ro...@ma...> - 2003-12-04 18:40:54
|
For those who are interested and development-inclined... I've posted the bulk of the new source base on my iDisk. This isn't a full user-level release yet as a couple components still need to be finished. For those who are looking for something new to tinker with and fixes for many of the problems and features that weren't addressed by earlier versions, this would be a good place for you to start. What is included: interface-independent PRISM device control driver partially completed PCCard interface driver What is NOT yet included: user-level apps userClient interface for applications Framework for application development The remaining components are still being rewritten and will be added soon. I'll also be adding this new code to the main project CVS tree in the coming week as I get a chance. I don't have any objections if someone with more time on their hands than I do right now wants to submit some code to fill in the blanks and will graciously accept any additions or bug fixes, giving credit where credit is due. ...due to iDisk bandwidth, it may still be several hours before the archive is completely uploaded. You are looking for a file named "WirelessDriver2prerelease.sit" -Rob McKeever ro...@ma... -- /* drunk.. fix later */ |
|
From: Java N. <jav...@ho...> - 2003-12-02 14:36:35
|
I am wondering, does anyone have support digests before #474 and/or devel digests before #64 that you could share with me, as I just recently subscribed to these lists? I have been noticing that the archives of the list at sourceforge have been dropping a few messages, so the archives are not complete. Thanks in advance. _________________________________________________________________ Is there a gadget-lover on your gift list? MSN Shopping has lined up some good bets! http://shopping.msn.com |
|
From: Java N. <jav...@ho...> - 2003-11-24 15:26:23
|
I removed my card and then put my computer to sleep. When I woke it up it Kernal panicked (showing the message to restart in several languages). Has anyone had this bug effect them in this manner? I thought I heard a Kernal panic can occur when reinserting a card after removal, but that was not what I did, but I am not sure of the exact circumstances that trigger the bug (and how reproducible - occassional or every time) and would like more information on the bug and whether it will be fixed in the next version. Thanks in advance _________________________________________________________________ Gift-shop online from the comfort of home at MSN Shopping! No crowds, free parking. http://shopping.msn.com |
|
From: Rob M. <ro...@ma...> - 2003-11-19 03:02:06
|
On 18-Nov-03, at 6:50 PM, Java Nut wrote:
> Hi Rob,
>
> Regarding the fact I did not see the system warning when I first
> inserted my PRISM 2.5 card, but did see it when I (second) inserted my
> Orinoco card makes me think the driver was not invoked at all for the
> PRISM 2.5 card. (I just clicked for the system to fix and use when I
> did get the message and the Orinoco card came up fine in the driver
> (checked with ifconfig).)
So you and everyone else knows, 10.3 no longer gives you the option to
fix broken driver permissions.
> Can you advise, if the following is how I should be setting up my XML
> in the Info.plist, and if there is something else I should be doing?
>
> The info I obtained from my card is:
>
> /usr/sbin/ioreg -l | grep VersionOneInfo
> | | "VersionOneInfo" = ("SMC","SMC2532W-B EliteConnect
> Wireless Adapter","","")
>
> /usr/sbin/ioreg -l | grep pccard
> | | +-o pccardd601,5@0,0 <class IOPCCard16Device>
> | | "IOName" = "pccardd601,5"
>
> I tried adding this to the configuration file like this and it did not
> help:
>
> <key>everything else</key>
> <dict>
> <key>CFBundleIdentifier</key>
>
> <string>org.noncontiguous.WirelessDriver</string>
> <key>IOClass</key>
>
> <string>org_noncontiguous_WirelessDriver</string>
> <key>IONameMatch</key>
> <array>
> <string>pccard156,2</string>
> <string>pccard1eb,807</string>
> <string>pccard274,1613</string>
> <string>pccard274,1612</string>
> <string>pccard138,2</string>
> <string>pccardd601,5</string>
> <------ added line
> </array>
>
> I am wondering, if you know a way I can verify that the card I
> purchased is really PRISM 2.5 and that the manufacturer didn't
> misspeak?
Hmmm... add extra logging to start() to make sure that the INIT command
completes and/or check the responses to RID queries?
The changes to the .plist file look good. That should be enough to get
it working right.
>
>> Due to demand, I think I'm going to bite the bullet and post >for
>> core of my new code later today even if I don't manage >to sort out
>> the bug I'm working on. Depending on how my day >goes, I likely
>> won't have the chance to post the PCCard >interface code for this
>> driver right away.
>
> I look forward to downloading and trying the new version.
...which will be posted as soon as I can get a night's sleep...
I kinda put my foot in my mouth while on the phone with a client the
other day and promised something in about half the time it should have
been allocated, so I'm going to be in save-my-ass mode for the next few
days. I'll try to get it up during a break.
>
> May I ask a couple more questions about how the code works.
>
>>> 3) I am curious, where in the code is the xml file read and >>the
>>> card type checked? And how does the program >>distinguish what
>>> PRISM level a card has?
>
>> That is done by IOKit automatically. For information on how this
>> works, see
>> ><http://developer.apple.com/documentation/DeviceDrivers/Conceptual/
>> IOKitFundamentals/index.html>
>
> So, then, where is the entry point of the driver, and how is the
> driver told which card was inserted?
I'd recommend going through Apple's IOKit tutorials and reference docs
for that. The basics are easy, but some of the complexities can take a
while to wrap your head around.
Basically, the .plist file specifies the class name for IOKit to load.
IOKit then probes it to make sure it can load (probe returns a score.
Higher is better with 0 being this dirver shouldn't try loading), then
init(), followed by start(). If the best matching driver can't init or
start properly, then it tries the next best and so on.
>
>>> I noticed that some messages were written to /var/log/system.log
>>> when I inserted my >>Orinoco (but not for the PRISM 2.5 card):
>
> How are messages written to /var/log/system.log?
Magic! :-) IOLog handles this. Look through xnu and/or IOKit for
details.
I've put code in my new version to log via USBProber and the KLog.kext
driver. This makes it much more user-friendly to deal with. That code
will be posted shortly.
>
> Thanks for all your help.
>
No problem. I just wish I had more time to do this stuff right now.
-Rob
|
|
From: Java N. <jav...@ho...> - 2003-11-19 02:50:25
|
Hi Rob,
Regarding the fact I did not see the system warning when I first inserted my
PRISM 2.5 card, but did see it when I (second) inserted my Orinoco card
makes me think the driver was not invoked at all for the PRISM 2.5 card. (I
just clicked for the system to fix and use when I did get the message and
the Orinoco card came up fine in the driver (checked with ifconfig).) Can
you advise, if the following is how I should be setting up my XML in the
Info.plist, and if there is something else I should be doing?
The info I obtained from my card is:
/usr/sbin/ioreg -l | grep VersionOneInfo
| | "VersionOneInfo" = ("SMC","SMC2532W-B EliteConnect
Wireless Adapter","","")
/usr/sbin/ioreg -l | grep pccard
| | +-o pccardd601,5@0,0 <class IOPCCard16Device>
| | "IOName" = "pccardd601,5"
I tried adding this to the configuration file like this and it did not help:
<key>everything else</key>
<dict>
<key>CFBundleIdentifier</key>
<string>org.noncontiguous.WirelessDriver</string>
<key>IOClass</key>
<string>org_noncontiguous_WirelessDriver</string>
<key>IONameMatch</key>
<array>
<string>pccard156,2</string>
<string>pccard1eb,807</string>
<string>pccard274,1613</string>
<string>pccard274,1612</string>
<string>pccard138,2</string>
<string>pccardd601,5</string> <------
added line
</array>
I am wondering, if you know a way I can verify that the card I purchased is
really PRISM 2.5 and that the manufacturer didn't misspeak?
>Due to demand, I think I'm going to bite the bullet and post >for core of
>my new code later today even if I don't manage >to sort out the bug I'm
>working on. Depending on how my day >goes, I likely won't have the chance
>to post the PCCard >interface code for this driver right away.
I look forward to downloading and trying the new version.
May I ask a couple more questions about how the code works.
>>3) I am curious, where in the code is the xml file read and >>the card
>>type checked? And how does the program >>distinguish what PRISM level a
>>card has?
>That is done by IOKit automatically. For information on how this works, see
> ><http://developer.apple.com/documentation/DeviceDrivers/Conceptual/
>IOKitFundamentals/index.html>
So, then, where is the entry point of the driver, and how is the driver told
which card was inserted?
>>I noticed that some messages were written to /var/log/system.log when I
>>inserted my >>Orinoco (but not for the PRISM 2.5 card):
How are messages written to /var/log/system.log?
Thanks for all your help.
_________________________________________________________________
Gift-shop online from the comfort of home at MSN Shopping! No crowds, free
parking. http://shopping.msn.com
|
|
From: Java N. <jav...@ho...> - 2003-11-18 14:53:13
|
Here is how I set up my XML hack for my SMC2532W-B, which is also a PRISM
2.5 card. Do you know a way I can verify the chipset in my card that the
manufacturer told me correctly what chipset they have in it?
/usr/sbin/ioreg -l | grep VersionOneInfo
| | "VersionOneInfo" = ("SMC","SMC2532W-B EliteConnect
Wireless Adapter","","")
/usr/sbin/ioreg -l | grep pccard
| | +-o pccardd601,5@0,0 <class IOPCCard16Device>
| | "IOName" = "pccardd601,5"
I tried adding this to the configuration file like this:
<key>everything else</key>
<dict>
<key>CFBundleIdentifier</key>
<string>org.noncontiguous.WirelessDriver</string>
<key>IOClass</key>
<string>org_noncontiguous_WirelessDriver</string>
<key>IONameMatch</key>
<array>
<string>pccard156,2</string>
<string>pccard1eb,807</string>
<string>pccard274,1613</string>
<string>pccard274,1612</string>
<string>pccard138,2</string>
<string>pccardd601,5</string>
</array>
I use OS X 10.2.6.
Thanks in advance for any help.
>
>On Nov 17, 2003, at 7:36 AM, Java Nut wrote:
>>Has anyone started to look at supporting any PRISM 2.5 card before, or am
>>I the first interested?
>
>I use one all the time with the stock driver. Prism 3 should work fine
>also. I'd check your XML hacks since the driver did not get called per
>your description.
>
>Cheers,
>Cliff
>
_________________________________________________________________
Crave some Miles Davis or Grateful Dead? Your old favorites are always
playing on MSN Radio Plus. Trial month free!
http://join.msn.com/?page=offers/premiumradio
|
|
From: Rob M. <ro...@ma...> - 2003-11-17 18:28:35
|
On 17-Nov-03, at 7:36 AM, Java Nut wrote: > Hi Rob, > > Thank you for your reply. I have a few more followup questions before > I am ready to look at this in more detail. > >> AN9900 and RM025 are available under NDA from Intersil. >> sorry, I can't share them without breaking that agreement. > > Do you have contact information or know where on the web to get the > NDA? I believe they were taken over by another company. Lucent and CHOICE worked together to develop the original silicon for the PRISM 2 and Hermes chipsets. CHOICE was bought by Intersil and Lucent later spun their wireless stuff off as OriOCO which was bought by Proxim (I think). Intersil took their technology and continued to develop it into the PRISM 2.5 and PRISM 3 chipsets, then designed an entirely new set of chips for the PRISM GT, PRISM DUO, etc. It seems they have recently (since I last checked) sold that stuff off to GlobespanVirata. <http://www.globespanvirata.com/prism.html> > >> PRISM 2, 2.5 and 3 are all very similar. The biggest differences are >> in form factor and integration. I >> believe that RPSIM 2 was very similar silicon to Lucent's Hermes >> chipset and that PRISM 2.5 introduced >> USB as an interface type. > > If this is the case, it would seem that it should be simple to get it > to work, if it already handles PRISM 2.0. But I am not sure if the > code even recognizes when I insert my card. When I recompiled the code > and first inserted my PRISM 2.5 card, and then my Orinoco WaveLan, the > program gave an OSX security warning asking whether I want to fix, > use, or don't use the kernal extension, but this was not displayed > until I inserted my Orinoco. The PRISM 2.5 card does not show up in > ifconfig's output. OK, this is an IOKit issue, not a driver issue... IOKIt looks at it's XML Info.plist file for each driver it knows of. Then tries to start each matching driver for that device, starting with the best match and working downwards until it finds one that starts successfully. Beginning with Jaguar, IOKit checks each driver's ownership and read/write permissions prior to allowing it to be used by the system for security. If you're getting that alert, then these settings are at fault and the systsem won't load your the driver until they're fixed. Try running "kextload -t ..." against the driver, fixing whatever it whines about, then touching the Extensions directory to force a rebuild of the kext caches. > >>> 3) I am curious, where in the code is the xml file read and the card >>> type checked? And how >>> does the program distinguish what PRISM level a card has? >> That is done by IOKit automatically. For information on how this >> works, >> see >> <http://developer.apple.com/documentation/DeviceDrivers/Conceptual/ >> IOKitFundamentals/ >> index.html> > > So, are you saying that control is then never turned over to our code > if the card is not listed in the file? (I had added the card info to > the XML, but it did not help for my PRISM 2.5 card.) Yes, that is correct. > >> IOLog() written messages are written to the system console. The >> location of this varies from >> system release to system release but is easily accessed by the >> Console app. Some of them >> are written when compiled as a release build, but these are >> generally restricted to error messages. > > I noticed that some messages were written to /var/log/system.log when > I inserted my Orinoco (but not for the PRISM 2.5 card): > > Nov 14 12:52:59 Latinums-Computer mach_kernel: IOPCCard info: > IOPCCard16Enabler::configure using index 0x01: Vcc 5.0, irq 255, io > 0x0000-0x003f > Nov 14 12:52:59 Latinums-Computer mach_kernel: > org_noncontiguous_WirelessDriver: _wi_readChipInfos() > Nov 14 12:52:59 Latinums-Computer mach_kernel: > org_noncontiguous_WirelessDriver: Firmware version: 1-8.40 > Nov 14 12:52:59 Latinums-Computer mach_kernel: > org_noncontiguous_WirelessDriver: Default channel 10 > Nov 14 12:52:59 Latinums-Computer mach_kernel: > org_noncontiguous_WirelessDriver: Ethernet address 00:02:2d:64:8f:d3 These appear to be messages from our driver. > >> Not yet. Much of the existing code base was pulled from NetBSD. I >> do have a new code base that >> will be released as soon as I can sort out one last bug that hangs >> certain card firmware. I'm hoping this is in the next day or two. > > Does your new code base add support for any more cards (especially the > high output cards)? Is WEP support improved? The high-output cards are PRISM 2.5 cards and are known to work. I have added WEP support to my new codebase and it works for both 40-bit and 128-bit WEP. My new codebase was designed specifically for the PRISM firmware, so might require some tweaking to get WEP working properly with older WaveLAN cards. > > Has anyone started to look at supporting any PRISM 2.5 card before, or > am I the first interested? I've been running a handful of PRISM 2.5 cards without issue on both the current codebase and my new code for the past 2 years or so. Due to demand, I think I'm going to bite the bullet and post for core of my new code later today even if I don't manage to sort out the bug I'm working on. Depending on how my day goes, I likely won't have the chance to post the PCCard interface code for this driver right away. -Rob |
|
From: Java N. <jav...@ho...> - 2003-11-17 15:37:01
|
Hi Rob, Thank you for your reply. I have a few more followup questions before I am ready to look at this in more detail. >AN9900 and RM025 are available under NDA from Intersil. >sorry, I can't share them without breaking that agreement. Do you have contact information or know where on the web to get the NDA? I believe they were taken over by another company. >PRISM 2, 2.5 and 3 are all very similar. The biggest differences are in >form factor and integration. I >believe that RPSIM 2 was very similar silicon to Lucent's Hermes chipset >and that PRISM 2.5 introduced >USB as an interface type. If this is the case, it would seem that it should be simple to get it to work, if it already handles PRISM 2.0. But I am not sure if the code even recognizes when I insert my card. When I recompiled the code and first inserted my PRISM 2.5 card, and then my Orinoco WaveLan, the program gave an OSX security warning asking whether I want to fix, use, or don't use the kernal extension, but this was not displayed until I inserted my Orinoco. The PRISM 2.5 card does not show up in ifconfig's output. >>3) I am curious, where in the code is the xml file read and the card type >>checked? And how >>does the program distinguish what PRISM level a card has? >That is done by IOKit automatically. For information on how this works, >see <http://developer.apple.com/documentation/DeviceDrivers/Conceptual/ >IOKitFundamentals/ >index.html> So, are you saying that control is then never turned over to our code if the card is not listed in the file? (I had added the card info to the XML, but it did not help for my PRISM 2.5 card.) >IOLog() written messages are written to the system console. The location >of this varies from >system release to system release but is easily accessed by the Console >app. Some of them >are written when compiled as a release build, but these are generally >restricted to error messages. I noticed that some messages were written to /var/log/system.log when I inserted my Orinoco (but not for the PRISM 2.5 card): Nov 14 12:52:59 Latinums-Computer mach_kernel: IOPCCard info: IOPCCard16Enabler::configure using index 0x01: Vcc 5.0, irq 255, io 0x0000-0x003f Nov 14 12:52:59 Latinums-Computer mach_kernel: org_noncontiguous_WirelessDriver: _wi_readChipInfos() Nov 14 12:52:59 Latinums-Computer mach_kernel: org_noncontiguous_WirelessDriver: Firmware version: 1-8.40 Nov 14 12:52:59 Latinums-Computer mach_kernel: org_noncontiguous_WirelessDriver: Default channel 10 Nov 14 12:52:59 Latinums-Computer mach_kernel: org_noncontiguous_WirelessDriver: Ethernet address 00:02:2d:64:8f:d3 >Not yet. Much of the existing code base was pulled from NetBSD. I do >have a new code base that >will be released as soon as I can sort out one last bug that hangs certain >card firmware. I'm hoping this is in the next day or two. Does your new code base add support for any more cards (especially the high output cards)? Is WEP support improved? Has anyone started to look at supporting any PRISM 2.5 card before, or am I the first interested? _________________________________________________________________ Great deals on high-speed Internet access as low as $26.95. https://broadband.msn.com (Prices may vary by service area.) |
|
From: Paul R. <st...@st...> - 2003-11-16 23:11:30
|
On Monday, Nov 17, 2003, at 05:10 Australia/Sydney, Rob McKeever wrote: > > Not yet. Much of the existing code base was pulled from NetBSD. I do > have a new code base that will be released as soon as I can sort out > one last bug that hangs certain card firmware. I'm hoping this is in > the next day or two. Out of curiosity, is this the older NetBSD code base, or the unified NetBSD/FreeBSD IEEE 802.11 imported into NetBSD by David Young in the last few months? Cheers, -- Paul Ripke Unix/OpenVMS/TSM/DBA I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams |
|
From: Rob M. <ro...@ma...> - 2003-11-16 18:11:19
|
On 16-Nov-03, at 8:34 AM, Java Nut wrote: > I downloaded the latest source code using CVS as described in the FAQ > and I might have some time to take a stab at PRISM 2.5 support. First > I have a few questions that would help me get started: > > 1) Have any of the other developers found the PRISM 2.0 and PRISM 2.5 > programmer's manuals by Intersil? Can you share them with me or make > them available on the sourceforge site for the project? AN9900 and RM025 are available under NDA from Intersil. sorry, I can't share them without breaking that agreement. > > 2) Has anyone looked at how different or similar PRISM 2.5 is to PRISM > 2.0? PRISM 2, 2.5 and 3 are all very similar. The biggest differences are in form factor and integration. I believe that RPSIM 2 was very similar silicon to Lucent's Hermes chipset and that PRISM 2.5 introduced USB as an interface type. > > 3) I am curious, where in the code is the xml file read and the card > type checked? And how does the program distinguish what PRISM level a > card has? That is done by IOKit automatically. For information on how this works, see <http://developer.apple.com/documentation/DeviceDrivers/Conceptual/ IOKitFundamentals/index.html> > > 4) Where are the messages written by IOLOG written? and are they > written when the project is compiled with the release project setting? IOLog() written messages are written to the system console. The location of this varies from system release to system release but is easily accessed by the Console app. Some of them are written when compiled as a release build, but these are generally restricted to error messages. > > 5) Are there any notes about the overall structure and organization of > the program to help me understand the program quickly? Not yet. Much of the existing code base was pulled from NetBSD. I do have a new code base that will be released as soon as I can sort out one last bug that hangs certain card firmware. I'm hoping this is in the next day or two. > > Thanks in advance for any assistance. > -Rob McKeever ro...@ma... |
|
From: Java N. <jav...@ho...> - 2003-11-16 16:35:13
|
I downloaded the latest source code using CVS as described in the FAQ and I might have some time to take a stab at PRISM 2.5 support. First I have a few questions that would help me get started: 1) Have any of the other developers found the PRISM 2.0 and PRISM 2.5 programmer's manuals by Intersil? Can you share them with me or make them available on the sourceforge site for the project? 2) Has anyone looked at how different or similar PRISM 2.5 is to PRISM 2.0? 3) I am curious, where in the code is the xml file read and the card type checked? And how does the program distinguish what PRISM level a card has? 4) Where are the messages written by IOLOG written? and are they written when the project is compiled with the release project setting? 5) Are there any notes about the overall structure and organization of the program to help me understand the program quickly? Thanks in advance for any assistance. _________________________________________________________________ Concerned that messages may bounce because your Hotmail account is over limit? Get Hotmail Extra Storage! http://join.msn.com/?PAGE=features/es |
|
From: Keith M. <te...@li...> - 2003-08-28 06:13:58
|
I was looking at the CVS directory and noticed that it hasn't been updated in a while. Will the new source be posted or how close is the general release? Thanks for all your work! |
|
From: Michael A. B. <mb...@ma...> - 2003-06-30 16:01:57
|
Has anyone made any progress getting the wireless driver to work with the skyline PCI adapter? michael |
|
From: RJ A. <rj...@vo...> - 2003-06-03 00:33:03
|
Rob, I would love to give this a try. I have a TiBook running 10.2.6 with several versions of the lucent/orinoco cards for testing. RJ On Sunday, May 25, 2003, at 23:34 US/Pacific, Rob McKeever wrote: > A while back I mentioned that I had a new version that I have been > working on for some time that has all of the missing features that > everybody's been begging for. How many adventurous soles are there > out there that would be interested in testing and/or bug fixing for a > new and improved version? > > It's almost ready for general release. I'm having some minor issues > with the PCCard interface still but the rest has been running stable > for some time in a similar form with a USB interface (sorry - can't > release the USB code due to the contract terms). There are one or two > small issues I know of that are being worked on still, but it does > support WEP on all Intersil PRISM cards and can do the same for > WaveLAN and Airport cards with some small changes. It also supports > network scanning on newer firmware (I haven't looked into the > differences between new and old firmware, so I won't guarantee that > yet). > > Anyone interested should drop me line so I have a current list. I'll > be ready to drop code to those willing/able to assist with the final > bits sometime tomorrow (Monday) evening. A general release likely > won't be far behind. > > -Rob > ro...@ma... |
|
From: Kenton A. H. <sh...@ma...> - 2003-05-30 17:59:59
|
Interested. Ti 1GHz/1GB with about five different kind of cards to play with. --On Sunday, May 25, 2003 23.34 -0700 Rob McKeever <ro...@ma...> wrote: > A while back I mentioned that I had a new version that I have been working > on for some time that has all of the missing features that everybody's been > begging for. How many adventurous soles are there out there that would be > interested in testing and/or bug fixing for a new and improved version? > > It's almost ready for general release. I'm having some minor issues with > the PCCard interface still but the rest has been running stable for some > time in a similar form with a USB interface (sorry - can't release the USB > code due to the contract terms). There are one or two small issues I know > of that are being worked on still, but it does support WEP on all Intersil > PRISM cards and can do the same for WaveLAN and Airport cards with some > small changes. It also supports network scanning on newer firmware (I > haven't looked into the differences between new and old firmware, so I > won't guarantee that yet). > > Anyone interested should drop me line so I have a current list. I'll be > ready to drop code to those willing/able to assist with the final bits > sometime tomorrow (Monday) evening. A general release likely won't be far > behind. > > -Rob > ro...@ma... > > > > ------------------------------------------------------- > This SF.net email is sponsored by: ObjectStore. > If flattening out C++ or Java code to make your application fit in a > relational database is painful, don't do it! Check out ObjectStore. > Now part of Progress Software. http://www.objectstore.net/sourceforge > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel -- | Kenton A. Hoover / Private Citizen / sh...@ma... | |
|
From: Alf W. <al...@ma...> - 2003-05-27 20:57:28
|
More than happy to help test. I have a TiBook 500 with an assortment of cards to play with. I'm also interesting in getting a code drop to integrate with iStumbler. Best, Alf On Sunday, May 25, 2003, at 11:34 p, Rob McKeever wrote: > Anyone interested should drop me line so I have a current list. I'll > be ready to drop code to those willing/able to assist with the final > bits sometime tomorrow (Monday) evening. A general release likely > won't be far behind. |
|
From: Rob M. <ro...@ma...> - 2003-05-26 06:35:15
|
A while back I mentioned that I had a new version that I have been working on for some time that has all of the missing features that everybody's been begging for. How many adventurous soles are there out there that would be interested in testing and/or bug fixing for a new and improved version? It's almost ready for general release. I'm having some minor issues with the PCCard interface still but the rest has been running stable for some time in a similar form with a USB interface (sorry - can't release the USB code due to the contract terms). There are one or two small issues I know of that are being worked on still, but it does support WEP on all Intersil PRISM cards and can do the same for WaveLAN and Airport cards with some small changes. It also supports network scanning on newer firmware (I haven't looked into the differences between new and old firmware, so I won't guarantee that yet). Anyone interested should drop me line so I have a current list. I'll be ready to drop code to those willing/able to assist with the final bits sometime tomorrow (Monday) evening. A general release likely won't be far behind. -Rob ro...@ma... |
|
From: Rob F. <fr...@ww...> - 2003-03-26 18:41:25
|
Hi All, The SigMeter enhancements I put in last Christmas time have been submitted to the CVS. They include the following: 1) Help is present 2) Signal to noise ratio reading 3) Noise level 4) Signal level is now an option 5) In addition to graphical readout, quantitative measurements are available. These are accurate for Wavelan cards, but are not correct for EnGenius, and probably others. I kind of know how to fix this, but haven't yet. 6) New graphical icons are used. That is about all I remember at this time. Thanks, Rob -- Rob Frohne, Ph.D., P.E. E.F. Cross School of Engineering Walla Walla College http://www.wwc.edu/~frohro/ |
|
From: Mike M. <mi...@ma...> - 2003-02-28 01:56:49
|
Thanks for the reply Amanda... i've started checking out other projects to see how things are done. if anyone out there knows of any projects that would be a good example of this please let me know... thanks, mike On Thursday, February 27, 2003, at 08:31 PM, Amanda Walker wrote: > Mike Marcucio <mi...@ma...> wrote: >> I got the following info from robm(thanks for >> the reply): >> >> "How does scanning work? You issue RID FCE1 or FCE5 (but not both >> together) and wait for a few seconds. The system will return an info >> frame containing the hosts and some info on them. If you don't get >> this, you can manually request it after 3 seconds." > > Unfortunately, scanning isn't even close to that simple. It depends > on the brand of card and the revision of the firmware. Intersil > firmware before 1.3.2 does it one way, 1.3.2 and up do it another way, > early Orinoco firmware does it a third way, and current Orinoco > firmware does it a fourth way. They vary in how you kick off a scan, > whether or not you lose your current association to an AP while it > does the scan, how you gather the results, and what format the results > are in. Some drivers provide an API that hides this complexity > "behind the scenes" for you, though. > > From a programming point of view, the simplest device to deal with is > probably an Orinoco card. I can't give you a code snippet, but there > are some examples out there in various open source drivers for other > platforms. > > > Amanda Walker > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel > |
|
From: Amanda W. <am...@al...> - 2003-02-28 01:32:57
|
Mike Marcucio <mi...@ma...> wrote: > I got the following info from robm(thanks for > the reply): > > "How does scanning work? You issue RID FCE1 or FCE5 (but not both > together) and wait for a few seconds. The system will return an info > frame containing the hosts and some info on them. If you don't get > this, you can manually request it after 3 seconds." Unfortunately, scanning isn't even close to that simple. It depends on the brand of card and the revision of the firmware. Intersil firmware before 1.3.2 does it one way, 1.3.2 and up do it another way, early Orinoco firmware does it a third way, and current Orinoco firmware does it a fourth way. They vary in how you kick off a scan, whether or not you lose your current association to an AP while it does the scan, how you gather the results, and what format the results are in. Some drivers provide an API that hides this complexity "behind the scenes" for you, though. From a programming point of view, the simplest device to deal with is probably an Orinoco card. I can't give you a code snippet, but there are some examples out there in various open source drivers for other platforms. Amanda Walker |
