All of lore.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] Kernel Modules for ARM
Date: Tue, 27 Jun 2006 10:47:48 +0200	[thread overview]
Message-ID: <1151398068.25011.10.camel@localhost> (raw)
In-Reply-To: <6297d67c0606270126k2217235fwbc7fd3b56b1007dc@mail.gmail.com>

Hi Mayank,

> I already have a 2.4.21 kernel running, but I cannot see any of the
> kernel modules for BlueZ, e.g. bluez.o, l2cap.o, rfcomm.o in the
> directory /lib/modules/kernel.
>  
> So does that mean that my kernel was compiled without Bluetooth
> support?
> - If yes, is there any way with which I can enable Bluetooth support?
> (Will I have to recompile the kernel?)
> - Or can I directly apply some patch by which I can get those kernel
> modules?

you will have to re-compile the kernel if no additional kernel modules
package is available.

Regards

Marcel



Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2006-06-27  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  5:42 [Bluez-devel] Kernel Modules for ARM Mayank Batra
2006-06-27  7:37 ` Marcel Holtmann
2006-06-27  8:26   ` Mayank Batra
2006-06-27  8:32     ` Mayank Batra
2006-06-27  8:48       ` Marcel Holtmann
2006-06-27  8:47     ` Marcel Holtmann [this message]
2006-06-27  9:56     ` Peter Wippich
2006-06-27 10:47       ` Mayank Batra

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=1151398068.25011.10.camel@localhost \
    --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 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.