VERY OBSOLETE linux-wlan-ng master repository
Find a file
1999-11-11 17:05:34 +00:00
doc Makefile updates for clean target 1999-11-04 08:08:39 +00:00
man Makefile updates for clean target 1999-11-04 08:08:39 +00:00
scripts Makefile updates for clean target 1999-11-04 08:08:39 +00:00
src Initial checkin. 1999-11-11 17:05:34 +00:00
config.mk Finished init code, about to test 1999-11-10 19:47:10 +00:00
Makefile Added file clean stuff. 1999-11-04 08:25:01 +00:00
README Updated README for code delivery 1999-11-11 17:00:07 +00:00

Top level directory for linux-wlan-ng.

./doc		- source distribution documentation
./man		- man pages
./scripts	- scripts used at run-time
./src		- source code for various components

Note:
Some of the subdirectories have empty README files.  This means we haven't 
gotten to the contents of these directories.  The empty README is just a trick
to prevent CVS from pruning the directory.

Build Instructions:

1) untar the package using

   tar zxvf linux-wlan-ng.tar.gz

or you can use winzip with the file  linux-wlan-ng.tar.

2) Make sure you have configured kernel and pcmcia sources on your system.

3) Modify the config.mk file, here's a description of the settings:

LINUX_SRC	Path to your kernel source tree
PCMCIA_SRC	Path to your pcmcia source tree
MODULES_DIR	Path to your modules directory, use by 'make install'
INST_EXEDIR	Path to your static bin directory
DESTDIR=	Alternate desination prefix for install

Note:  I haven't tested the install, I'm not sure that all of the components 
will make it to their appropriate destinations.

4) Execute the 'make all' command 

5) Since we don't have any actual devices yet, you can try loading the modules
   by hand.  Here's the sequence:

   insmod src/p80211/p80211.o
   insmod src/skeleton/skelwland_cs.o

 now do the following command:

   ifconfig wlan0

 You should see that the wlan0 interface exisits.  You can try configuring
 wlan0.  BEWARE, it might leave your system unstable!  The skeleton driver
 is just a demonstation and test fixture, it skips over alot of stuff a
 real driver is supposed to do.  You can confirm the skeleton methods being
 called by checking your kernel.* output via syslog (you might have to edit
 syslog.conf, most distributions send kernel.* to /dev/null by default).  Using
 this same method you should be able to run wlanctl to send commands down
 to the driver.  It won't act on them, but it will write an entry to the log
 indicating receipt.