[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] Making stack for Axis etrax lx board. newbie
I accidently sent this mail to the etrax list, sorry!
On Mon, 16 Jul 2001, Park Duck Gun wrote:
> Thanks for kind message.
> As I do make changes , I encountered two problem.
> 1) Can you explain it more ?
> "Copy the whole linux directory with subdirectories from the openbt directory on to the kernel source tree. Make sure that you copy the directory correctly so that the trees matches. E g the include directory of the stack is copied into the include directory in the kernel source tree."
> As I make copies , I copyed the bluetooth directory to the kernel
> directory. To match the include in the bluetooth directory and include
> directory directory in kernel directory. But I was not sure about the
> apps & src directory in the bluetooth directory. So I just made apps &
> src directory in the root of kernel directory and copyed files.
What OpenBT version are you using? I'm using OpenBT 0.0.5 and it works.
The newer releases have a different directory structure than the older
ones and seems to be more prepared for compilation into the kernel. I
haven't tried it on any other release than 0.0.5, so I suggest that you
download the 0.0.5 instead. The apps directory shouldn't be compiled into
the kernel. It contains applications that you can compile and run to test
communication between modules, when you have a working stack.
> 2) drivers/char/bluetooth/Config.in file is required. How can I make the
> Config.in file
The Config.in file is just information for the kernel configuration. When
you add the "source drivers/char/bluetooth/Config.in" line in the
Config.in file in the drivers/char directory, you should see a Bluetooth
menu in the Character Device menu when you run "make xconfig" or "make
menuconfig" to configure the kernel.
> -----Original Message-----
> From: firstname.lastname@example.org [mailto:owner-bluetooth-
> email@example.com]On Behalf Of Marcus Jonsson
> Sent: Saturday, July 14, 2001 11:05 PM
> To: Park Duck Gun
> Cc: bluetooth dev
> Subject: Re: [bluetooth-dev] Making stack for Axis etrax lx board.
> I had the same problem, but I hope I have a workable solution to it now.
> > Hi,
> > I want to make the stack for the developer board lx.
> > Can anybody show me the rough direction of how to make it for board?
> > Thanks
> Since you can't insmod a module into the kernel on the development board (at least with the standard software), the only way to do it (as far as I know) is to statically compile the stack into the kernel. I wanted to find a patch that would insert the source code for the stack into the kernels source tree, but didn't find one. So this is how I did it:
> Make sure that you have run the patches included in the development board software (this is done by the install program) on the kernel source tree.
> Copy the whole linux directory with subdirectories from the openbt directory on to the kernel source tree. Make sure that you copy the directory correctly so that the trees matches. E g the include directory of the stack is copied into the include directory in the kernel source tree.
> Edit the Makefile file in the kernel source "drivers/char" directory, by adding:
> subdir-$(CONFIG_BLUETOOTH) += bluetooth
> ifeq ($(CONFIG_BLUETOOTH),y)
> obj-y += bluetooth/bt.o
> Now edit the file Config.in file by adding:
> source drivers/char/bluetooth/Config.in
> somewhere in the file but before the endmenu command.
> You should now have a Bluetooth menu in the Character Devices menu in the kernel configuration program.
> This is the way I have done it and it seems to work for me. I am able to communicate with a Bluetooth module through serial communication, but I haven't tested it thoroughly.
> If this isn't a good way to do it, I would be happy to know.
> Best regards
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
> the body of a message to firstname.lastname@example.org
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com