[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

New release 0.0.6 (was RE: [bluetooth-dev] Problem: 'insmod bt.o')



FYI there is now a new release 0.0.6 available on SourceForge.
It should fix the problem mentioned below amongst others.

//Peter

> -----Original Message-----
> From: Peter Kjellerstedt [mailto:pkj@xxxxxxx.com]
> Sent: 16 August 2001 14:50
> To: 'embedded solutions'; bluetooth-dev@xxxxxxx.com
> Subject: RE: [bluetooth-dev] Problem: 'insmod bt.o'
> 
> > -----Original Message-----
> > From: embedded solutions [mailto:embedded_swe@xxxxxxx.com]
> > Sent: 16 August 2001 14:01
> > To: bluetooth-dev@xxxxxxx.com
> > Subject: [bluetooth-dev] Problem: 'insmod bt.o'
> > 
> > Hello,
> > 
> > After updating the 'init_env and the 'Makefile' according to the 
> > instructions found at wwww.sourceforge.net (version 0.0.5), I 
> > try to install the stack on a PC running on RedHat7.1.
> > When I try to insmod the 'bt.o' file into the kernel i get 
> > the following message:
> > 
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol hci_receive_acl
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol hci_receive_bcsp
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol hci_receive_event
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol csr_waitcmdnum
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol hci_receive_hq
> > ./linux/drivers/char/bluetooth/bt.o: unresolved symbol bt_write_lower_driver_real
> > 
> > Do I insmod the correct file?
> > 
> > 
> > best regards
> > 
> > Tobbe
> 
> The problem is that with version 0.0.5 of the stack, the BCSP
> source files were built and included in the bt.o module, even
> if BCSP support was not wanted. You can either fix your
> Makefile to not include the BCSP files in the bt.o module,
> retrieve the current stack using CVS, or retrieve the updated
> Makefile via the sourceforge web-interface to the cvs repository.
> 
> //Peter
-
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to majordomo@xxxxxxx.com