From: Marcel Holtmann <marcel@holtmann.org>
To: jens.carroll@carroll.de
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] unresolved symbol __do_softirq
Date: Thu, 08 Jan 2004 18:29:57 +0100 [thread overview]
Message-ID: <1073582997.2563.14.camel@pegasus> (raw)
In-Reply-To: <3FFD4845.3090206@carroll.de>
Hi Jens,
> I have a problem integrating bluez into a cross complied kernel version
> 2.4.20. The target is a arm7tdmi and I used the latest patch for that
> kernel. The kernel compilation (bluez as modules) works fine and does
> not report any errors. However when I want to insmod the bluez.o I get:
>
> Using bluez.o
> insmod: unresolved symbol __do_softirq
>
> Well, I am not even sure it is a bluez or a kernel problem. The symbol
> __do_softirq is not exported (checked with "cat ksyms | grep __do_softirq").
I am no ARM expert so I can't help you, but from a quick search through
the kernel source I saw the __do_softirq is specific for the ARM arch.
Try to post this on an ARM mailing list.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2004-01-08 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 12:08 [Bluez-devel] unresolved symbol __do_softirq Jens Carroll
2004-01-08 17:29 ` Marcel Holtmann [this message]
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=1073582997.2563.14.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jens.carroll@carroll.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.