From: Simon Huggins <huggie@earth.li>
To: Marcel Holtmann <marcel@holtmann.org>,
BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] D-Link DBT 120 B4 - works in 2.4.26-mh1 not 2.6.6
Date: Fri, 14 May 2004 09:59:51 +0100 [thread overview]
Message-ID: <20040514085951.GL19473@paranoidfreak.co.uk> (raw)
In-Reply-To: <20040513222606.GE19473@paranoidfreak.co.uk>
On Thu, May 13, 2004 at 11:26:06PM +0100, Simon Huggins wrote:
> On Fri, May 14, 2004 at 12:18:35AM +0200, Marcel Holtmann wrote:
> > 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
> Ah right no I didn't since it didn't moan when I ran it as a user.
> If I do I get:
> HCIDump - HCI packet analyzer ver 1.5
> device: hci0 snap_len: 1028 filter: 0xffffffff
> < HCI Command: Inquiry(0x01|0x0001) plen 5
> 33 8B 9E 08 64
> > HCI Event: Command Status(0x0f) plen 4
> 00 01 01 04
> > HCI Event: Inquiry Complete(0x01) plen 1
> 00
> for a scan and the same for an inq.
In 2.4.26-mh1 I can see the phone I get:
huggie@thin:~$ sudo hcidump -x
HCIDump - HCI packet analyzer ver 1.5
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Inquiry(0x01|0x0001) plen 5
33 8B 9E 08 64
> HCI Event: Command Status(0x0f) plen 4
00 01 01 04
> HCI Event: Inquiry Result(0x02) plen 15
01 29 F4 36 6D 0E 00 01 00 00 04 02 52 46 6B
> HCI Event: Inquiry Complete(0x01) plen 1
00
< HCI Command: Remote Name Request(0x01|0x0019) plen 10
29 F4 36 6D 0E 00 02 00 00 00
> HCI Event: Command Status(0x0f) plen 4
00 01 19 04
> HCI Event: Remote Name Req Complete(0x07) plen 255
00 29 F4 36 6D 0E 00 53 68 69 6E 79 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
And the scan does see the device with the name I gave it.
Simon.
--
"Be wewy wewy careful. There be dragons here." -- Linus Torvalds
next prev parent reply other threads:[~2004-05-14 8:59 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
2004-05-13 22:26 ` Simon Huggins
2004-05-14 8:59 ` Simon Huggins [this message]
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=20040514085951.GL19473@paranoidfreak.co.uk \
--to=huggie@earth.li \
--cc=bluez-users@lists.sourceforge.net \
--cc=marcel@holtmann.org \
/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