public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] FW: Need some help - linux bluetooth driver
Date: Tue, 18 Sep 2007 06:58:19 +0200	[thread overview]
Message-ID: <1190091499.5525.108.camel@aeonflux.holtmann.net> (raw)
In-Reply-To: <6E672510D37D58428215BDFDF097DB46014692C9@EXGNT01.sasken.com>

Hi Pintu,

> I need a help in compiling the linux 2.4.22 code (bluetooth part).
> Can you help me here.

the Linux 2.4 part of BlueZ is actually no longer officially supported
and so you can't expect any real help here.

However the 2.4.22 might be recent enough to get you going and it
contains the Bluetooth core.

> Here is my problem description
> ==========================
> I have a linux system which is running on Linux 2.4.22-ncgl-10.12.1.0
> kernel. It is a modified kernel. 
> Here the BLUETOOTH part is removed from the kernel. 
> (I didnt find - hci_core , hci_conn.o , and other required drivers and
> some of the export symbols are missing)
> (It report un resolved symbols - "hci_register_dev")

Since this looks like a vendor specific kernel that you have paid for,
it might be better to complain with that company and make them include
the Bluetooth sources again. I am serious here.

> I have the 2.4.22-ncgl-10.12.1.0 kernel source with me (on another
> system).
> Now, I dont want to build the whole kernel again. (This is not
> possible as it is in another system under separate path)
>  
> I wanted to compile only the Bluetooth related path (net/bluetooth/*)
> from this kernel source and put all related stuffs on my system.
> Is it possible??????? Please let me know the procedure. Please help me
> out.

So in theory it is possible to compile the kernel modules outside the
kernel source tree, but I don't remember the exact steps for a 2.4
system and quite frankly, I am not going to look that up.

The best way is to go for a 2.6.22 kernel or later. It might look
complicated in the beginning, but it is always worth the extra work. It
will give you a recent Bluetooth stack that is known to be qualifiable
and is up-to-date.

Regards

Marcel



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-09-18  4:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  4:15 [Bluez-devel] FW: Need some help - linux bluetooth driver Pintu Agarwal
2007-09-18  4:58 ` 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=1190091499.5525.108.camel@aeonflux.holtmann.net \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox