All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Simon Huggins <huggie@earth.li>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] D-Link DBT 120 B4 + 2.6.6 / 2.6.6-mh1
Date: Fri, 14 May 2004 00:18:35 +0200	[thread overview]
Message-ID: <1084486715.25099.164.camel@pegasus> (raw)
In-Reply-To: <20040513220010.GD19473@paranoidfreak.co.uk>

Hi Simon,

> Ok it shows:
> 	huggie@thin:~$ hcidump -x
> 	HCIDump - HCI packet analyzer ver 1.5
> 	device: hci0 snap_len: 1028 filter: 0xffffffff
> 	> HCI Event: Command Status(0x0f) plen 4
> 	  00 01 01 04 
> 	> HCI Event: Inquiry Complete(0x01) plen 1
> 	  00 

I miss the inquiry command. Do you ran hcidump as root? You must see
something like this:

	< HCI Command: Inquiry(0x01|0x0001) plen 5
	  33 8B 9E 08 64 
	> HCI Event: Command Status(0x0f) plen 4
	  00 01 01 04 

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-05-13 22:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 20:20 [Bluez-users] D-Link DBT 120 B4 + 2.6.6 / 2.6.6-mh1 Simon Huggins
2004-05-13 21:50 ` Marcel Holtmann
2004-05-13 22:00   ` Simon Huggins
2004-05-13 22:18     ` Marcel Holtmann [this message]
2004-05-13 22:26       ` Simon Huggins
2004-05-14  8:59         ` [Bluez-users] D-Link DBT 120 B4 - works in 2.4.26-mh1 not 2.6.6 Simon Huggins
2004-05-14 23:40           ` More progress with 2.6.6-mh1 Simon Huggins

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=1084486715.25099.164.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=huggie@earth.li \
    /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.