[Madwifi-devel] Armv5te EABI Hal needed for ixp425

[<ro...@li...>]

Dear Madwifi  ( maybe Dear Sam Leffler)

I am dealing with madwifi powered cards and i need to make them run on a
IXP425 Xscale board.
I am using openembedded to cross compile my whole stuff.
All is well , but now as i get to the point to compile the madwifi
drivers i got stuck in compiling / linking them
Some investigations and talks on both #oe and #madwifi made get closer
to my problem .

My linker is a eabi aware one , actually i use angstrom distribution
which is fully eabi compatibel.
When do a objdump -x  on any binary in my rootfs it get
private flags = 4000002: [Version4 EABI] [has entry point]
When i do objdump -x on your hal i get
objdump -x  madwifi/ath_hal/hal.o | grep flags
architecture: arm, flags 0x00000011:
private flags = 200: [APCS-32] [FPA float format] [software FP]
This is the exact difference mentioned for legacy arm and eabi arm under
http://wiki.debian.org/ArmEabiPort#head-c1b1150b6d0eb3a0120117a81b4fa725cf9301b1

The following error i get when linking

LD [M]  /madwifi/ath_hal/ath_hal.o
| armeb-angstrom-linux-gnueabi-ld: ERROR: Source object
madwifi/ath_hal/hal.o has EABI version 0, but target
/madwifi/ath_hal/ath_hal.o has EABI version 4

Could you please advice me what i can do to either:
a) get a hal file which is eabi v4
b) pay someone at atheros to get me this
c) use "some magic " compatibility mode in order to ignore it.
d) tell me what i still do wrong or think wrong

As i understood the hal is required to be binary according to FCC
regulations so noone can change frequency`s and such.

Please Sam  Tell us what we need to do . Those atheros cards are the
best products we found for our project as they have high range and good
transmit powers.
The whole product is targeted to become a router on cargo ships.

Waiting patiently for your suggestions

Robert Wörle