From: Marcel Holtmann <marcel@rvs.uni-bielefeld.de>
To: "Jan J. Jessen" <jjjessen@control.auc.dk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Digianswer USB driver
Date: 17 Sep 2003 01:57:15 +0200 [thread overview]
Message-ID: <1063756641.29941.26.camel@pegasus> (raw)
In-Reply-To: <Pine.GSO.4.40.0309161558370.18622-100000@prosit.control.auc.dk>
Hi Jan,
> I've now tried the patch and compiled a new kernel with hci_usb as a
> module.
> When I load it into the kernel I get the following:
>
> # insmod /lib/modules/2.4.22/kernel/drivers/bluetooth/hci_usb.o
> /lib/modules/2.4.22/kernel/drivers/bluetooth/hci_usb.o: unresolved symbol
> hci_register_dev_Rsmp_17de4405
> /lib/modules/2.4.22/kernel/drivers/bluetooth/hci_usb.o: unresolved symbol
> hci_unregister_dev_Rsmp_380d73d1
> /lib/modules/2.4.22/kernel/drivers/bluetooth/hci_usb.o: unresolved symbol
> hci_recv_frame_Rsmp_75250b00
>
> I've used a "fresh" 2.4.22 kernel
try it again, because this is a problem with MODVERSION. Maybe the
running kernel or bluez.o module is compiled without and the hci_usb.o
driver with it.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-09-16 23:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-15 6:25 [Bluez-devel] Digianswer USB driver Jan J. Jessen
2003-08-15 12:39 ` Marcel Holtmann
2003-08-26 11:24 ` Jan J. Jessen
2003-08-30 0:11 ` Marcel Holtmann
2003-09-16 14:02 ` Jan J. Jessen
2003-09-16 23:57 ` Marcel Holtmann [this message]
2003-09-17 9:59 ` Jan J. Jessen
2003-09-22 17:59 ` Marcel Holtmann
2003-09-23 8:21 ` Jan J. Jessen
2003-09-23 8:56 ` Marcel Holtmann
2003-09-29 10:58 ` Jan J. Jessen
2003-09-16 14:16 ` Jan J. Jessen
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=1063756641.29941.26.camel@pegasus \
--to=marcel@rvs.uni-bielefeld.de \
--cc=bluez-devel@lists.sourceforge.net \
--cc=jjjessen@control.auc.dk \
/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.