readme.linux

atmel芯片的Linux驱动程序。很多802.11协议的无限网卡都使用该芯片

This file contains useful information about Winter for Linux


authors: The Winter team


i) INSTALLATION FROM SOURCES
-------------------------------------------------------------------------------

	Step I:
	Since Winter requires wxWindows, you will have to succesfully download and setup wxGTK-2.4.0.
	Please, refer to www.wxwindows.org for downloading instructions. After downloading the tarball,
	you are ready to install wxWindows.
	To build wxWindows perform the following steps:
		- extract tarball to a directory of your choice
		- change to wxWindows root dir
		- $ mkdir build; cd build
		- $ ../configure --with-gtk --disable-shared --enable-debug --enable-debug_gdb
		- $ make
		- get suid
		- $ make install
		- $ ldconfig
	If everything has gone as expected, wx will now have been installed. To check whether the installation
	was succesful type:
		- $ wx-config --version
	The wxWindows version should appear on the screen.


	Step II:
	If atmelwlan drivers and pcmcia card services have not already been installed
	you had better do it now. For installation and configuration sources and details
	refer to the correspondig sources:
	for pcmcia	 :		http://pcmcia_cs.sf.net
	for atmelwlan:		http://atmelwlandrivers.sf.net


	Step III:	( atmel cvs specific for the moment ) 
	At this point you can safely proceed with Winter installation.
	Change to the dir where you wish Winter to be installed and do a cvs 
	checkout as follows:
	$ cvs -d :pserver:username@cyanodus:/ATMEL_CVS/Drivers login 
	$ cvs -d :pserver:username@cyanodus:/ATMEL_CVS/Drivers co Winter
	For linux, run "make linux" at Winter/bin directory, or just "make" 
	under Winder/bin/linux .
	In the latter dir, winter executable is created, after a successful compilation.
	Obviously, winter can only run under x enviroment.
	Because of the "under development" stage of the application, only debug
	compilation is provided for now, but this is certainly subject to change.


ii) INSTALLATION FROM BINARIES
-------------------------------------------------------------------------------
	No binary distribution available yet. :(
	Considering about rpm and deb packages.


iii) BUILDING OPTIONS
-------------------------------------------------------------------------------
	Winter basic functionality may be configured through the WinterSetup.h header file.
	The following settings are available :
		- ENABLE_DEBUG_MESSAGES
		  	Toggles the output of the debug messages.
		  
			Possible values :
		  		0 if you want to prevent the debug messages from being printed,
		  		1 if you want to be printed.

		- FRAME_WIDTH, FRAME_HEIGHT
			Set the initial (which is also the minimum) size of the main frame (in pixels).

			Possible values :
				Theoritically any positive integer.
				Practically, a width of 600 pixels and a height of 650 is recommended.

		- MAIN_TIMER_INTERVAL
			Set the interval of the timer that updates the interface (Progress bars, statistics, etc) in milliseconds.

			Possible values :
				Theoritically any positive integer, however 1000 msecs is recommended.

		- DELAY_AFTER_SUBMIT
			Enables or disables the application delay after pressing any of the "Submit" or 'Apply" buttons.

			Possible values :
		  		0 to disable delay 
		  		1 to enable delay

		- USE_BUSY_INFO
			This option is only effective if the DELAY_AFTER_SUBMIT option is set to 1. Enables or disables a message
			window to be appeares while delaying showing a message like "Configuring...". Due to a bug, setting this option
			to 1 under the  RedHat8 and RedHat9 desktop environment will lead winter, and maybe X server itself, to a crash.

			Possible values :
				0 to disable the message window
				1 to enable the message window

		- CHECK_SINGLE_INSTANCE
			If this option is set to 1, the application will check whether another instance is currently running. This would
			be the default behaviour, but sometimes, especially during the development and after heavy crashes, some nagging
			messages were shown. If this is not a problem for you, we recommend setting this option to 1. It is much safer.

			Possible values :
				0 to disable the checker
				1 to enable the checker

		-USE_LOCALE
			If this option is set to 1, the application loads message catalogs which contain the translations of the strings used to the current language.If this option is set to 0 default language( english ) is used.
			If language catalog winter.mo is not found then default language ( english ) will be used.

			possible values :
				0 to disable locale
				1 to enable locale


iv) FEATURES
-------------------------------------------------------------------------------
	- All configuration commands can be issued to the device. Statistics and several other miscellaneous options are available,
	as well. 

	- Profile page is available with a preview of all saved profiles. The profile page allows the user to save the current 
	settings under a profile name, load a previously saved profile and remove a selected profile. All profiles are written
	listed in a choice control to be easy and quick every time to activate (APPLY) the selected profile. Each  profile settings are stored
	in the file ~/.winter/profilesrc.
	Note : Avoid modifying this file by hand because validity check is not fully implemented in this version.

	- All essid's used until the application terminates are kept in a combobox providing "ease of reuse".

	- The application is able to support any language. Winter loads message catalogs (.mo) which contain the translations of the strings used.
	  Adding a new language support is easy.
	  
	  	a) At first, a .po file must be created:
			$ make
			Now, a messages.po file must have been created. Rename it to xx.po (where xx is the two letter ISO country code). Edit its header as necessary.

		b) Patch the first line of the Makefile, adding the two letter country code.
			For example: AVAIL_LOCALES:=el de xx
		c) Now edit the new xx.po file, translating each message listed.
		d) $ make
			Now, a directory named xx should have been created, containing the xx.mo file. (which is the compiled po file)
		e) Edit the WinterLang.cpp source file. Read the comments and add support for your language using the WINTER_LANG macro.
			For examble : WINTER_LANG( wxT( "Deutsch" ), wxLANGUAGE_DEUTSCH ) to add support for the german language. wxT( "Deutsch" )
			is the string representing the "user friendly"-"human-readable" string of the language. wxLANGUAGE_DEUTSCH is the
			wxWindows language code. Please, refer to the URL mentioned in the WinterLang.cpp file for more details.
		f) Rebuild winter.
		g) All message catalogs should be placed at:
			- usr/share/locale/xx/LC_MESSAGES
			- usr/local/share/locale/xx/LC_MESSAGES
		If everything is ok, winter will now support the new language.


v) KNOWN ISSUES
-------------------------------------------------------------------------------
	No, currently, pending issues.


vi) TODO's
-------------------------------------------------------------------------------
	No future plans are available at the moment.