Return-Path: Subject: Re: [Bluez-devel] Digianswer USB driver From: Marcel Holtmann To: "Jan J. Jessen" Cc: BlueZ Mailing List In-Reply-To: References: Content-Type: text/plain Message-Id: <1063756641.29941.26.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: 17 Sep 2003 01:57:15 +0200 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