Add targets for both HAL binaries without $(obj), which is needed for
Linux 2.4 build system. Keep targets with $(obj) for Linux 2.6.
Use $(HALBIN) for non-unmangled HAL and $(HALOBJ) for unmangled HAL.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3836 0192ed92-7a03-0410-a25b-9323aeb14dbd
Conversions in place should be avoided in the build system because make
doesn't know if the conversion has taken place. Use a different name
for HAL before unmangling. Respect the build quietness settings.
Simplify Linux 2.4 rules so that the commands for decoding and
unmangling are written only once.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3815 0192ed92-7a03-0410-a25b-9323aeb14dbd
They appeared:
- in generic code and PARISC - in 2.6.12
- in PPC64 - in 2.6.14
- in merged PowerPC - in 2.6.15 (when the merge occurred)
- in MIPS - in 2.6.21
Improve comments and indentation, as the logic is getting more complex.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3712 0192ed92-7a03-0410-a25b-9323aeb14dbd
According to FreeBSD changelog, this area is present in 5416 and newer
and must be byteswapped on big-endian systems. Testing confirms it.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3701 0192ed92-7a03-0410-a25b-9323aeb14dbd
This should fix compilation on little-endian ARM and possibly other
platforms with little or no optimization. This closes#1783.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3700 0192ed92-7a03-0410-a25b-9323aeb14dbd
Remove kbuild by-products in regression/Makefile. Also allow
regression/tkip/test_tkip.c to compile (too few arguments to function
ieee80211_crypto_demic).
Closes: #1973
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3699 0192ed92-7a03-0410-a25b-9323aeb14dbd
Otherwise, $(TARGET).hal.o is not built for Linux 2.4 kernels. The rule
for ath_hal.o is for Linux 2.4 only and should not affect Linux 2.6
builds.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3604 0192ed92-7a03-0410-a25b-9323aeb14dbd
During the second stage of the module build, Linux 2.6.26 does not
define $(obj). Try using $(SUBDIRS) as $(obj) before falling back to
the current directory.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3603 0192ed92-7a03-0410-a25b-9323aeb14dbd
Filter out harmful options from OBJCOPY. Linux 2.4 adds "-O binary" and
"-S" for i386 and x86_64, which would break the build.
Use $(TOP) in hal_unmangle.objcopy path.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3599 0192ed92-7a03-0410-a25b-9323aeb14dbd
Normally, compatibility issues should be addressed in compat.h, but
INITIAL_JIFFIES is not something that should be widely used.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3598 0192ed92-7a03-0410-a25b-9323aeb14dbd
1) Move all debug preprocessor flags out into make files
2) Add support for remaining preprocessor flags to be set by ENV variables
3) Add support for HAL tracing to include device name
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3481 0192ed92-7a03-0410-a25b-9323aeb14dbd
both i386 and x86_64. When calculating TARGET for x86 platform, use
CONFIG_X86 and CONFIG_X86_64 rather than ARCH.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@3318 0192ed92-7a03-0410-a25b-9323aeb14dbd
The architectures that don't set CONFIG_GENERIC_IOMAP are supposed to
provide replacements for functions in lib/iomap.c, but not all provide
iowrite32be() and ioread32be().
Only MIPS, PARISC and PowerPC implement iowrite32be and ioread32be as
functions, while SH and AVR32 provide macros. Other architectures, in
particular ARM, provide no replacement at all.
This should fix ticket #1539.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@2932 0192ed92-7a03-0410-a25b-9323aeb14dbd
Fix inconsistent formatting of the comments. Fix the text along the
way. Run the file through madwifi-indent, but undo some overzealous
formatting.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@2931 0192ed92-7a03-0410-a25b-9323aeb14dbd
Linux 2.6.24 introduces a sysctl checker that disallows using arbitrary
ctl_name values for sysctl entries. The entries with non-standard
values should set ctl_name to CTL_UNNUMBERED.
On the other hand, using consistent non-zero ctl_name values is required
for older kernels (tested on Linux 2.4.33.3 from Slackware 11).
Thus the solution is to use CTL_UNNUMBERED on Linux 2.6.24+ and the
original values in the older kernels. Move CTL_AUTO and DEV_ATH to
include/compat.h and define them correspondingly.
When copying sysctl entries, check procname for being non-zero, since
ctl_name is zero (CTL_UNNUMBERED) on Linux 2.6.24 and newer.
For the same reason, don't use ctl_name to distinguish entries in
ath_sysctl_template, use extra2 instead.
git-svn-id: http://madwifi-project.org/svn/madwifi/trunk@2814 0192ed92-7a03-0410-a25b-9323aeb14dbd