Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Robert Wörle" <robert@linuxdevelopment.de>
To: openembedded-devel@lists.openembedded.org
Subject: ixp425 vs madwifi with armv5te big endian AND EABI error
Date: Tue, 12 Jun 2007 19:56:45 +0200	[thread overview]
Message-ID: <466EDE5D.7060304@linuxdevelopment.de> (raw)

Dear Openembedded Devel List

Iam developing a least cost router based on the Intel ixp425 CPUI and
some minipci slots. ( Board ADI Pronghorn-Metro).

Iam now infront of a problem where i would like ask for assistance.

The madwifi driver which powers the atheros wifi cards ( quite some wide
range also on multiband cards) uses firmware code tobe linked into their
drivers.
Now as i need to crosscompile my build fails like this
 LD [M]
/tmp/work/ixp4xxbe-angstrom-linux-gnueabi/madwifi-modules-1.0.0+cvs20060814-r0/madwifi/ath_hal/ath_hal.o
| armeb-angstrom-linux-gnueabi-ld: ERROR: Source object
/tmp/work/ixp4xxbe-angstrom-linux-gnueabi/madwifi-modules-1.0.0+cvs20060814-r0/madwifi/ath_hal/hal.o
has EABI version 0, but target
/mp/work/ixp4xxbe-angstrom-linux-gnueabi/madwifi-modules-1.0.0+cvs20060814-r0/madwifi/ath_hal/ath_hal.o
has EABI version 4


My suspicion is that the this binary code was compiled oabi hence eabi v
0. But the rest off all is of course eabi compiled.

will i need to get a armv5te firmware supporting this ?
is it an option to go oabi on my whole toolchain ? ( if yes point me to
side effects and ways to go, please)

I am kinda lost now .. what can i do ?

Kind Regards
rob_w




                 reply	other threads:[~2007-06-12 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=466EDE5D.7060304@linuxdevelopment.de \
    --to=robert@linuxdevelopment.de \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox