From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluetooth Printing (Belkin Print Server)
Date: Wed, 24 Nov 2004 07:06:36 +0100 [thread overview]
Message-ID: <1101276396.27351.92.camel@pegasus> (raw)
In-Reply-To: <41A3B992.7080202@phaldor.co.uk>
Hi Dave,
> Sorry for the stupid question, here are the results you asked for.
please attach them as *.txt files.
And the information so far are looking a little bit weird. For the
serial port they use UUID32 and for HCRP they use UUID16. I've never
seen this before.
However may you wanna force it to use the serial port profile. I haven't
tried this for a long time, but actually this URI should do it:
bluetooth://0002724080A3/spp
In hcidump you should now see a connection to RFCOMM channel 3 (DLCI 6).
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-11-24 6:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 15:41 [Bluez-users] Bluetooth Printing (Belkin Print Server) Dave Givens
2004-11-22 16:09 ` Marcel Holtmann
2004-11-22 17:05 ` Dave Givens
2004-11-22 17:16 ` Dave Givens
2004-11-23 9:16 ` Stefan Behlert
2004-11-23 9:40 ` Marcel Holtmann
2004-11-23 15:49 ` Dave Givens
2004-11-23 16:10 ` Marcel Holtmann
2004-11-23 16:21 ` Dave Givens
2004-11-23 16:36 ` Marcel Holtmann
2004-11-23 17:20 ` Dave Givens
2004-11-23 17:26 ` Marcel Holtmann
2004-11-23 22:28 ` Dave Givens
2004-11-24 6:06 ` Marcel Holtmann [this message]
2004-11-23 16:11 ` Stefan Behlert
2004-11-23 18:57 ` Dave Givens
2004-11-24 10:18 ` Stefan Behlert
2004-11-25 1:08 ` Dave Givens
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=1101276396.27351.92.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