From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Kernel Modules for ARM
Date: Tue, 27 Jun 2006 09:37:31 +0200 [thread overview]
Message-ID: <1151393851.25011.7.camel@localhost> (raw)
In-Reply-To: <6297d67c0606262242q11b6e769r15a48f1edffaa759@mail.gmail.com>
Hi Mayank,
> I am successfully able to cross-compile bluez-libs-2.25 and
> bluez-utils-2.25 for ARM.
>
> But I feel that the kernel modules (like bluez.o, l2cap.o, rfcomm.o
> etc) have not been built for ARM. (Or if they have been built
> somewhere, but I can't find them)
>
> So, if I say insmod bluez on my target, it says:
>
> # insmod bluez
> Using /lib/modules/kernel/bluez.o
> insmod: ELF file not for this architecture
> insmod: Could not load the module: Bad address
>
> I have the feeling that the bluez.o is not an ELF file and it was not
> generated during the cross compile.
the kernel modules for BlueZ are part of the Linux kernel. Pick a recent
kernel and you get all of them. And you should really go ahead with a
2.6 kernel. It is worth any initial trouble.
Regards
Marcel
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-27 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 5:42 [Bluez-devel] Kernel Modules for ARM Mayank Batra
2006-06-27 7:37 ` Marcel Holtmann [this message]
2006-06-27 8:26 ` Mayank Batra
2006-06-27 8:32 ` Mayank Batra
2006-06-27 8:48 ` Marcel Holtmann
2006-06-27 8:47 ` Marcel Holtmann
2006-06-27 9:56 ` Peter Wippich
2006-06-27 10:47 ` Mayank Batra
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=1151393851.25011.7.camel@localhost \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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