To learn how to submit patches please read our Submitting patches guideline. Read this section on Atheros specifications and documentation. This is a collection of bug reports both unresolved and resolved to help users track issues and to find patches for fixes which have not yet been merged. Please when submitting a bug report always include your card's silicon revision for MAC and PHY chips, just look at your kernel log for a line like this one… or.
User Tools Log In. Site Tools Search. Sidebar Users main page. Vendor Support. Driver Development. Table of Contents About Ath5k. The Linux wireless compatibility package - the most easy way to get and install the latest versions on all stable kernels.
The Linux kernel from version 2. However, we recommend to use at least 2. The Linux kernel 2. We recommend to install the Linux wireless compatibility package if you are running this kernel and your internet connection is slow or unreliable. This file is primarily an arrangement of constants, storage structures, and the like for the Atheros cards.
The extent to which this type of work is copyrightable is debatable. However, the parts that are likely to be copyrightable—the arrangements and representations of the structures—are clearly very different from corresponding parts in the ar5k files. Macros have been refactored, various define s have been organized into enum s, numerous typedef s have been changed to match Linux style, and some function prototypes have changed.
Finally, the presentation of the material has been rearranged and reorganized. They are derived from source code released in conjunction with the Atheros proprietary HALs that were once the focus of Madwifi development. The file primarily includes constants and structures related to the card. Again, the copyrightability of such work is minimal, but the presentation of the factual information about the card layout, which is the primary copyrightable component, has been changed substantially.
The information has been reorganized and renamed, and the macros have been refactored to fit Linux style. Ar5k treated each version of the card differently, while ath5k-driver instead has generalized functions for card operations. While some functions here are substantially similar, creative and careful work has adapted the return values for Linux. Meanwhile, in many functions some minor refactoring is found. The most substantial and the most substantive changes relate to the generalization of the functions.
Careful work has been done to abstract away the differences between the versions of the card and to make each function operate on all cards. In many cases, if statements have been created to handle special cases for particular cards whereas in ar5k, an entirely different function is used. It corresponds primarily to arreg. For example, ar5k uses macros to build various tables:.
There are few changes to the constants and numerical tables. Unlike the other header files, these constants and data concerning the card appear to be very close to the presentation of these constants and data in ar5k. In many cases in this file, the ath5k-driver function represents a merger of ar5k functions that were unique to specific chipsets. The two files are presented in mostly the same way, with a global rename of the various constants.
There is some minor refactoring in some places. However, the principal creative work added in ath5k-driver consists of comments regarding the purpose of the various constants. This addition is clearly a copyrightable change. The constants themselves, and the names they are given, particularly where a name represents a standard way of describing the purpose of the constant, will often fall outside the scope of copyright.
However, the arrangement, organization, presentation, and comments regarding the constants are almost certainly within scope of copyright, and the developers of both ar5k and the ath5k-driver have contributed to those components.
The copyright notices for all such contributors should appear in this file, but those examining the file should note that the copyright does not actually cover the facts that the file presents, only the arrangement and descriptions of those facts.
No additional copyrights were claimed by ath5k-driver developers, since hardly any changes were made, and those that were are almost certainly outside the scope of copyright.
Again, there are no additional copyrights by ath5k-driver developers; it appears that the only change made was a renaming. While under development, the software that ultimately became the ath5k-driver was hosted in various places.
0コメント