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: Mike M. <mi...@ma...> - 2003-02-27 04:35:20
|
Hello all, I'm still looking onto scanning for this driver. I know there is a lot of interest in this and someone has to do it. I looked over all the code in cvs and did some playing around. Now I'm ready to go ahead and get a sample app to scan. 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." I am not too familiar with how this should all work so i was wondering if i could get some more info. I just have a few questions that would help get this moving quicker. The first one is that i see a bunch of RIDs in if_wi_iee.h but i don't see any FCE1 or FCE5, maybe i'm just looking in the wrong place. also where would be the correct place/file to add this functionality? i'm sure once i get the frame with the hosts and info i could run with it from there, but i think i might need a little boost ;) Thanks and any info would be useful, mike |
|
From: Alf W. <al...@ma...> - 2003-02-17 22:50:35
|
Rob, If you're planning on using the same interface for the USB and OpenSource wireless drivers could you add the header file to CVS or just send it to the list? This would allow me to support scanning from USB wireless cards now and PC Card wireless in iStumbler once the new driver is released. Best, Alf On Sunday, February 16, 2003, at 08:57 p, Rob McKeever wrote: > I've got this working in a version of the driver written for USB > devices (for Macsense - www.macsense.com) and am rolling this code > into a new version that will be out soon. It's been delayed over and > over again due to other work, bugs found, family emergencies, burnout, > etc. but I am trying to get it out. > > -Rob > > On Sunday, February 16, 2003, at 06:15 PM, Mike Marcucio wrote: > >> I am wondering if there is any work on scanning going on? the airport >> driver has a WirelessScan function that returns a list of available >> networks, is there anything like this implemented or being worked on >> for this driver? I am interested in doing something like this but I >> do not want to dublicate effort. Can someone out there please let me >> know what is goin on? >> thanks and good job on the driver, >> mike >> >> >> >> ------------------------------------------------------- >> 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 >> > -- > "Quidquid latine dictum sit, altum viditur." > > > > ------------------------------------------------------- > 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: Rob M. <ro...@ma...> - 2003-02-17 04:57:42
|
I've got this working in a version of the driver written for USB devices (for Macsense - www.macsense.com) and am rolling this code into a new version that will be out soon. It's been delayed over and over again due to other work, bugs found, family emergencies, burnout, etc. but I am trying to get it out. -Rob On Sunday, February 16, 2003, at 06:15 PM, Mike Marcucio wrote: > I am wondering if there is any work on scanning going on? the airport > driver has a WirelessScan function that returns a list of available > networks, is there anything like this implemented or being worked on > for this driver? I am interested in doing something like this but I do > not want to dublicate effort. Can someone out there please let me know > what is goin on? > thanks and good job on the driver, > mike > > > > ------------------------------------------------------- > 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 > -- "Quidquid latine dictum sit, altum viditur." |
|
From: Mike M. <mi...@ma...> - 2003-02-17 02:24:38
|
I am wondering if there is any work on scanning going on? the airport driver has a WirelessScan function that returns a list of available networks, is there anything like this implemented or being worked on for this driver? I am interested in doing something like this but I do not want to dublicate effort. Can someone out there please let me know what is goin on? thanks and good job on the driver, mike |
|
From: Matthew C. <cal...@ma...> - 2003-01-16 02:05:16
|
Hello, I'm attempting to get the latest source using the commands in the FAQ. When I attempt to log in, if I just hit Return at the password prompt, as the FAQ suggests, the connection is refused. Is there now a password, or should I be doing something differently? Thanks, Matt |
|
From: Michel D. <wir...@mi...> - 2003-01-03 05:05:38
|
> I've inquired with TI, Atheros, Atmel, etc. and none of them has been > willing to give me the hardware interface documents I'd need to give > it a shot. I did manage to get a copy of the Atmel reference driver > source for Linux, but going from other source code means spending a > lot of time trying to sort out what is implementation-specific vs. > actually needed for talking to that device. > > If anyone wants to (or thinks they can) help with getting access to > the docs and/or samples from any of these vendors or others, please > try. I'd love to expand the project beyond what it already is, even > though it will take some time. Would you mind sharing your current conversations with the different companies, as it might help me take another shot at TI. And give the reference driver source that you managed to get, I can still take a look at it. You can email me directly if you wish so (for >300K xfers, please talk to me first). Mike |
|
From: Rob M. <ro...@ma...> - 2003-01-03 03:15:27
|
Hmmm... how to answer that one.. Basically, it will require rewriting almost the entire driver. The DWI-650+ uses a chipset from Texas Instruments that uses an entirely different MAC structure and communications setup. You can't just run a packet sniffer to figure it out, because most of the stuff going out over the air will appear standard, based on the 802.11 protocols. We'd need to convince TI to give us the information on the chipset, learn how to use it, get some sample hardware and then spend some serious time tinkering. I've inquired with TI, Atheros, Atmel, etc. and none of them has been willing to give me the hardware interface documents I'd need to give it a shot. I did manage to get a copy of the Atmel reference driver source for Linux, but going from other source code means spending a lot of time trying to sort out what is implementation-specific vs. actually needed for talking to that device. If anyone wants to (or thinks they can) help with getting access to the docs and/or samples from any of these vendors or others, please try. I'd love to expand the project beyond what it already is, even though it will take some time. -Rob On Thursday, January 2, 2003, at 07:01 PM, Michel Donais wrote: > Hi. > > Although I don't have a lot of time on my hands (too many projects, > too little time), I am quite interested in one of the D-Link DWI-G650 > card, which sports 54Mbps access... and I'm quite sure it's not > supported yet by the wirelessdriver driver (since even the 650+ is not > implemented). > > The big question is : how difficult would it be to create such a > driver and what does it requires? > > If it's a lot of packet sniffing with a supported PC, and checking how > data flows through their driver and trying to decipher how it works, > I'd forget it. > > If it's mainly getting public documentation, getting the wd source > code and adding a few twists and nudges, as well as maybe implementing > a few new functions and changing some packet informations, I'm in. > > If it's in-between, it all depends of your answer ^_^ > > > Have a nice day > Mike > > > > ------------------------------------------------------- > 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 > -- "Quidquid latine dictum sit, altum viditur." |
|
From: Michel D. <wir...@mi...> - 2003-01-03 03:01:55
|
Hi. Although I don't have a lot of time on my hands (too many projects, too little time), I am quite interested in one of the D-Link DWI-G650 card, which sports 54Mbps access... and I'm quite sure it's not supported yet by the wirelessdriver driver (since even the 650+ is not implemented). The big question is : how difficult would it be to create such a driver and what does it requires? If it's a lot of packet sniffing with a supported PC, and checking how data flows through their driver and trying to decipher how it works, I'd forget it. If it's mainly getting public documentation, getting the wd source code and adding a few twists and nudges, as well as maybe implementing a few new functions and changing some packet informations, I'm in. If it's in-between, it all depends of your answer ^_^ Have a nice day Mike |
|
From: Alf W. <al...@ma...> - 2002-12-30 21:26:38
|
Hello. I write a wireless scanning utility called iStumbler. Right now it works with Apples AirPort cards using the Apple80211.h interface. I'm getting requests for a version which works with PC Cards in G4 powerbooks. I know that there's work underway here on network scanning, and I'd like to ask for a way to sniff the raw 802.11 frames for finding hidden networks. iStumbler is open source under a BSD license and small (112K), so it could easily be bundled along with wireless driver once they work together. Best, Alf http://homepage.mac.com/alfwatt/istumbler |
|
From: Rob M. <ro...@ma...> - 2002-10-08 05:27:34
|
Frustration is... I've been a new version of the wirelessdriver that is much more powerful. AppleTalk works, it has network scanning, better WEP, etc. The catch is... some reason TCP/IP doesn't any more :-( ...thought someone out there could use a good chuckle... -Rob -- "Quidquid latine dictum sit, altum viditur." |
|
From: Rob M. <ro...@ma...> - 2002-08-29 08:33:24
|
I have just posted WirelessDriver 1.0.0b5.1 to both my iDisk (robm) and to the usual spot on SourceForge.net. This build has been tested much more extensively than the failed attempt I made a couple days ago and has shown itself to be quite stable. You can do a direct download from: <http://prdownloads.sourceforge.net/wirelessdriver/ WirelessDriverBeta5_1.dmg.sit?download> <http://ftp.sourceforge.net/wirelessdriver/ WirelessDriverBeta5_1.dmg.sit> This build has been compiled specifically for OS X 10.2 (Jaguar) and will not work on earlier versions of OS X. There will be a separate version coming shortly to fill this void. **PLEASE NOTE** There is an issue in this release with installing the driver over top of an existing version. It will fail the first time you try to do this (actually, it will fail every other time). If it fails, please try to run the installer at least once more before asking for assistance. The usual links: Project Support Home Page: <http://wirelessdriver.sourceforge.net> Project Support Mailing List: <http://lists.sourceforge.net/lists/listinfo/wirelessdriver- support> Project Announcemnets Mailing List: <http://lists.sourceforge.net/lists/listinfo/wirelessdriver- announce> Please try to post all support requests to the support list before contacting me or Yuriwho directly. This both helps to keep things organized and will likely get you a faster response. Thank you, -Rob McKeever ro...@ma... |
|
From: Rob M. <ro...@ma...> - 2002-08-25 22:28:26
|
Hi all, I've (finally) posted a build of the driver built for OS X 10.2 to my iDisk. The can be reached via the following URL: <http://homepage.mac.com/robm> This installer is a preliminary release. I will post it to SourceForge in the usual place and make an announcement to VersionTracker once I've had a few feedback reports. This build is, essentially, a top-of-tree build from the CVS archives. I have made several changes to it to support compilation under Jaguar and have added a few lines of code towards trying to solve the AppleTalk issue, although I haven't had any opportunity to test that yet. Let me know how you make out with it and I'll get whatever changes done that need to be made and make a final announcement. -Rob McKeever ro...@ma... |
|
From: Brian C M. <mi...@an...> - 2002-08-07 20:17:51
|
Hello, I was wondering if the current source compiles under 10.2? If not, are there any plans to do this work? Thanks, Brian |
|
From: David R. <db...@cs...> - 2002-07-25 23:02:57
|
Hello- I've made a small modification of the gui, now when you type in your network name, as soon as a match is found the WEP key is entered for you. -- Dave |
|
From: David R. <db...@cs...> - 2002-07-25 17:49:41
|
Hello - I have updated the CVS tree to reflect some fixes and additions to the Preference pane. 1) Fixed: clicking apply with blank WEP does not read keychain and fill in stored WEP key 2) Added: Signal to noise graph 3) Removed: tiffs for the signal to noise graph that are not being used. As far as the signal to noise graph is concerned the noise is normalized against the signal level and that percentage is the percentage is used to calculate the number of pixels for it to offset in the y-axis. Please tell me if you want the axis switched as I wasn't sure which was to go where. For switching networks, if you have logged in to a network before and clicked "Apply" and the wep key is stored in the key chain, all you need to do to reactivate a connection to that network (assuming the key is still unchanged) is type in the network name and click apply. -- Dave |
|
From: David R. <db...@cs...> - 2002-07-23 16:59:56
|
Hello - I've updated the wireless config project in CVS the following changes were made: UCWDAccess: Changed proceedure for PCCard Connections - will now have to call -(void)readPrefs to read preference files. Updated all other relevent files to have this change Added preliminary support for signal to noise graph (not yet enabled) Added new target for Signal Strength global menu. Created Signal strength meter using graphics that were provided by an unknown as of yet third party (waiting for a response from the furnisher as to how to give credit) I've also added in the startup item code in the WiConfigStartup folder, to use (use sudo): place the folder into /Library/StartupItems (you may need to create the folder) copy your org.noncontinuous.WirelessDriver.plist for ~/Library/Preferences to ~root/Library/Preferences (you may need to create the folders) I am working on the GUI for setting up the StartupItem and the Signal Strength meter. Expect an update to the credits for the signal strength meter soon as I will be updating that as soon as I get that information. -- Dave |
|
From: David R. <db...@cs...> - 2002-07-22 20:06:04
|
Hello I've just got a version of a menubar signal meter working. You can fetch it from http://touchstone.millersville.edu/~dbross/SigMeter.tar.gz. I need some feedback on it before I include it into the CVS and if anyone out there can design a better set of meter tiffs that would be helpful. (for those designing meter tiffs) Size limitations: height 16 pixels, width just keep it somewhat reasonable. 6 images ranging from no signal to full signal. Don't take other's copyrighted material. I also have a startup item ready, but it is as of now a bear to install, if you wish to use it email me and I'll send you the startup item and the directions. This will be released normally once I find a way of automating the install of it. -- Dave |
|
From: David R. <db...@cs...> - 2002-06-07 17:54:38
|
Hello, After getting responses back I found some errors in the GUI and fixed them, at the moment I need people to test if the GUI will work with 128bit airport passwords. Thanks. Changelog: *Fixed indexing for reading the popup menu to reflect reality (was based at index 1, now is based at index 0) *Enlarged the text box for the WEP field to better accommodate 128bit Hex keys -- Dave |
|
From: David R. <n1...@ma...> - 2002-06-06 16:15:09
|
Hello - I've just committed changes to the Preference Pane that need testing (I can't test them from school as there are no airport networks here.) 1) The ability to enter in Airport style passwords (requires that the airport software be installed) 2) The signal strength now has a united output, in dBm it is accurate to +/- 3 dBm. I only need the first checked out, especially on 128bit keys. To get the updated prefpane either email me or pull the latest sources and build from the CVS repository. Thanks, -- Dave |
|
From: Theron H. <the...@ya...> - 2002-06-01 22:09:21
|
sub generate_80211_key {
my($str) = @_;
return $1 if $str =~ /^\"(.....)\"$/;
return pack('H*', $2) if $str =~
/^(0[Xx]|\$)(..........)$/;
$whiten = pack('H*',
'16ebad570ff4e3de7d7472e8d2aba6a7');
$h1 = &md5($str . $whiten);
# md5z is like md5 but the chaining variables are
initialized to 0
$h2 = &md5z($h1);
$h3 = &md5z($h2);
# Use the first 5 bytes = 40 bits for reduced
strength
# Or use 13 bytes = 104 bits for almost-full
strength
return $h3;
}
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
|
|
From: Otto M. <ot...@dr...> - 2002-05-12 20:38:10
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hmm,
I don't seem to be able to compile the IOPCCardFamily driver. It gives
compile errors. I checked out the IOPCCardFamily project, double clicked
the project file (that gives an error saying that I am using an older
version of project builder, I am using version 1.1.1). Building then
fails:
In file included from pmueject/ApplePMUPCCardEject.cpp:23:
pmueject/ApplePMUPCCardEject.h:33: parse error before `{'
pmueject/ApplePMUPCCardEject.h:34: `ApplePMUPCCardEject' does not have a
nested type named `MetaClass'
...
I have to say that I never compiled darwin projects before, so maybe I
am doing something obviously wrong here.
The bridge card is a Texas Instruments PCI1410 PC card Cardbus
Controller (rev 01), the PCMCIA card is a SkyLine Prism card. All the
device details are in my first post
(<http://www.geocrawler.com/archives/3/16496/2002/4/0/8533990/>) ,
including some logging info and specific questions on config files,
maybe that already helps.
Otto
On vrijdag, mei 10, 2002, at 09:00 , Rob McKeever wrote:
> Be sure to tell me which build of IOPCCardFamily you use. I was
> talking to the person at Apple in charge of PCCard support in OS X and,
> apparently, PCI to PCMCIA/Cardbus adapters should work ok now. If
> you're still finding this to be a problem, let me know both the
> make/model of the card and the specific chip that it's using.
>
> -Rob
>
>
> On Thursday, May 9, 2002, at 10:59 PM, Otto Moerbeek wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>>
>> OK,
>>
>> I'll try to run the developer version of the IOPCCardFamily when I
>> find some time,
>>
>> Thanks,
>>
>> Otto
>>
>> On donderdag, mei 9, 2002, at 08:01 , Rob McKeever wrote:
>>
>>> pretty much accurate.
>>>
>>> There's 4 basic interfaces for the PRism chipset to be connected with:
>>> USB
>>> PC Card
>>> PCI
>>> "Airport", which is actually a variant of the ATA bus used for
>>> the CD-ROM drive
>>>
>>> Each one uses a different method to handle I/O, with USB and Airport
>>> being the most different. The PC Card and PCI versions are almost
>>> the same, but need to be handled differently because of the different
>>> bus interface mechanisms. Right now, the driver isn't checking to
>>> verify that it's really a PCCard interface, but will fail to map the
>>> memory if you hack it and it's really seeing something else.
>>>
>>>
>>> ...but...
>>>
>>> The PCI adapter you mention is a PCI to PCCard bridge card that uses
>>> an off-the-shelf PCCard to do the work. This should work, but it
>>> sounds like there's something wrong with the support in
>>> IOPCCardFamily that's preventing it from mapping the memory through
>>> to the end driver. I'd recommend getting the latest version of
>>> IOPCCardFamily from the Darwin CVS archive and compiling it in
>>> development mode and then sending a list of the output to me. I can
>>> look it over and file a bug report with Apple if it's needed.
>>>
>>
>>
>> - --
>> 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
>>
>> iD8DBQE822HF2/G1qy+3paMRAkczAJ4mR+B5XOqLysBneBTHYNJomCvR6QCgohQy
>> ppYNw5x0OvrCn336Jss6FRo=
>> =egaB
>> -----END PGP SIGNATURE-----
>>
>>
>> _______________________________________________________________
>>
>> Have big pipes? SourceForge.net is looking for download mirrors. We
>> supply
>> the hardware. You get the recognition. Email Us:
>> ban...@so...
>> _______________________________________________
>> Wirelessdriver-devel mailing list
>> Wir...@li...
>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We
> supply
> the hardware. You get the recognition. Email Us:
> ban...@so...
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
>
- --
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
iD8DBQE83tKN2/G1qy+3paMRAstEAJ0ecxcwRNVtoEq06e8GyQVjSDoDDgCgtNYo
BppZEZskitigf/m0K9J36YI=
=JWtv
-----END PGP SIGNATURE-----
|
|
From: Rob M. <ro...@ma...> - 2002-05-10 07:00:40
|
Be sure to tell me which build of IOPCCardFamily you use. I was talking to the person at Apple in charge of PCCard support in OS X and, apparently, PCI to PCMCIA/Cardbus adapters should work ok now. If you're still finding this to be a problem, let me know both the make/model of the card and the specific chip that it's using. -Rob On Thursday, May 9, 2002, at 10:59 PM, Otto Moerbeek wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > OK, > > I'll try to run the developer version of the IOPCCardFamily when I find some time, > > Thanks, > > Otto > > On donderdag, mei 9, 2002, at 08:01 , Rob McKeever wrote: > >> pretty much accurate. >> >> There's 4 basic interfaces for the PRism chipset to be connected with: >> USB >> PC Card >> PCI >> "Airport", which is actually a variant of the ATA bus used for the CD-ROM drive >> >> Each one uses a different method to handle I/O, with USB and Airport being the most different. The PC Card and PCI versions are almost the same, but need to be handled differently because of the different bus interface mechanisms. Right now, the driver isn't checking to verify that it's really a PCCard interface, but will fail to map the memory if you hack it and it's really seeing something else. >> >> >> ...but... >> >> The PCI adapter you mention is a PCI to PCCard bridge card that uses an off-the-shelf PCCard to do the work. This should work, but it sounds like there's something wrong with the support in IOPCCardFamily that's preventing it from mapping the memory through to the end driver. I'd recommend getting the latest version of IOPCCardFamily from the Darwin CVS archive and compiling it in development mode and then sending a list of the output to me. I can look it over and file a bug report with Apple if it's needed. >> > > > - -- > 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 > > iD8DBQE822HF2/G1qy+3paMRAkczAJ4mR+B5XOqLysBneBTHYNJomCvR6QCgohQy > ppYNw5x0OvrCn336Jss6FRo= > =egaB > -----END PGP SIGNATURE----- > > > _______________________________________________________________ > > Have big pipes? SourceForge.net is looking for download mirrors. We supply > the hardware. You get the recognition. Email Us: ban...@so... > _______________________________________________ > Wirelessdriver-devel mailing list > Wir...@li... > https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel |
|
From: Otto M. <ot...@dr...> - 2002-05-10 05:59:52
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 OK, I'll try to run the developer version of the IOPCCardFamily when I find some time, Thanks, Otto On donderdag, mei 9, 2002, at 08:01 , Rob McKeever wrote: > pretty much accurate. > > There's 4 basic interfaces for the PRism chipset to be connected with: > USB > PC Card > PCI > "Airport", which is actually a variant of the ATA bus used for the > CD-ROM drive > > Each one uses a different method to handle I/O, with USB and Airport > being the most different. The PC Card and PCI versions are almost the > same, but need to be handled differently because of the different bus > interface mechanisms. Right now, the driver isn't checking to verify > that it's really a PCCard interface, but will fail to map the memory if > you hack it and it's really seeing something else. > > > ...but... > > The PCI adapter you mention is a PCI to PCCard bridge card that uses an > off-the-shelf PCCard to do the work. This should work, but it sounds > like there's something wrong with the support in IOPCCardFamily that's > preventing it from mapping the memory through to the end driver. I'd > recommend getting the latest version of IOPCCardFamily from the Darwin > CVS archive and compiling it in development mode and then sending a > list of the output to me. I can look it over and file a bug report > with Apple if it's needed. > - -- 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 iD8DBQE822HF2/G1qy+3paMRAkczAJ4mR+B5XOqLysBneBTHYNJomCvR6QCgohQy ppYNw5x0OvrCn336Jss6FRo= =egaB -----END PGP SIGNATURE----- |
|
From: Rob M. <ro...@ma...> - 2002-05-09 18:01:12
|
pretty much accurate.
There's 4 basic interfaces for the PRism chipset to be connected with:
USB
PC Card
PCI
"Airport", which is actually a variant of the ATA bus used for the CD-ROM drive
Each one uses a different method to handle I/O, with USB and Airport being the most different. The PC Card and PCI versions are almost the same, but need to be handled differently because of the different bus interface mechanisms. Right now, the driver isn't checking to verify that it's really a PCCard interface, but will fail to map the memory if you hack it and it's really seeing something else.
...but...
The PCI adapter you mention is a PCI to PCCard bridge card that uses an off-the-shelf PCCard to do the work. This should work, but it sounds like there's something wrong with the support in IOPCCardFamily that's preventing it from mapping the memory through to the end driver. I'd recommend getting the latest version of IOPCCardFamily from the Darwin CVS archive and compiling it in development mode and then sending a list of the output to me. I can look it over and file a bug report with Apple if it's needed.
-Rob
On Monday, May 6, 2002, at 10:01 PM, yuriwho wrote:
> From my limited understanding, I do not believe this will be possible until
> apple includes support for PCMCIA cards via PCI into IOPCCardFamily.kext.
> You can try compiling the latest version of IOPCCardFamily from Apples cvs
> but I haven't seen anything in the change log to indicate that it could
> work. I defer to Rob for a more authoritative answer.
>
> Y
>
>
> On 4/30/02 1:42 AM, "Otto Moerbeek" <ot...@dr...> wrote:
>
>> -----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>,<04060000c5
>> 099172>
>> ,<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-----
>>
>>
>> _______________________________________________
>> Wirelessdriver-devel mailing list
>> Wir...@li...
>> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
>>
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: ban...@so...
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
|
|
From: yuriwho <yu...@ma...> - 2002-05-07 05:01:55
|
From my limited understanding, I do not believe this will be possible until
apple includes support for PCMCIA cards via PCI into IOPCCardFamily.kext.
You can try compiling the latest version of IOPCCardFamily from Apples cvs
but I haven't seen anything in the change log to indicate that it could
work. I defer to Rob for a more authoritative answer.
Y
On 4/30/02 1:42 AM, "Otto Moerbeek" <ot...@dr...> wrote:
> -----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>,<04060000c5
> 099172>
> ,<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-----
>
>
> _______________________________________________
> Wirelessdriver-devel mailing list
> Wir...@li...
> https://lists.sourceforge.net/lists/listinfo/wirelessdriver-devel
>
|
