Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] "hcitool dev" shows no devices
Date: Sun, 30 Jan 2005 21:15:16 +0100	[thread overview]
Message-ID: <1107116116.8384.4.camel@pegasus> (raw)
In-Reply-To: <41FD3E26.1000401@gmx.ch>

Hi Marco,

> I've a 2.4.26 kernel. I patched it using the "patch-2.4.26-mh2.gz" from the 
> bluez homepage. *
> Then, in "make menuconfig" I selected this points:
> # Bluetooth support -> Bluetooth subsystem support
> #                      L2CAP protocol support (NEW)
> #                      RFCOMM protocol support
> #                        RFCOMM TTY support (NEW)
> # Bluetooth support -> Bluetooth device drivers -> HCI USB driver (new)
> 
> Then I compiled and installed the new kernel.
> After that I compiled and installed the bluez-libs and bluez-utils.
> 
> Everything works well...
> Now I try "hcitool dev" but no devices are showed (I have two D-Link DBT120 
> connected to usb ports).
> 
> Any Ideas why they aren't recognized?
> Did I miss to add a feature to the kernel?

what does "hciconfig -a" say? What is in /proc/bus/usb/devices?

> * Something gets rejected during the patch (It doesn't seem important to 
> me, but maybee it is):
> 
> Makefile.rej:
> ***************
> *** 1,7 ****
>    VERSION = 2
>    PATCHLEVEL = 4
>    SUBLEVEL = 26
> - EXTRAVERSION =
> 
>    KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
> 
> --- 1,7 ----
>    VERSION = 2
>    PATCHLEVEL = 4
>    SUBLEVEL = 26
> + EXTRAVERSION = -mh2
> 
>    KERNELRELEASE=$(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)

You can ignore this one. It will almost fail if you don't use a vanilla
base.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-01-30 20:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-30 20:05 [Bluez-users] "hcitool dev" shows no devices Marco Trudel
2005-01-30 20:15 ` Marcel Holtmann [this message]
2005-01-30 20:40   ` Marco Trudel
2005-01-30 20:48     ` Marcel Holtmann
2005-01-30 21:11       ` Marco Trudel

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=1107116116.8384.4.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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