From: Marcel Holtmann <marcel@holtmann.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Printer adapter w/o SDP
Date: Sun, 18 Jul 2004 22:01:12 +0200 [thread overview]
Message-ID: <1090180872.4400.36.camel@pegasus> (raw)
In-Reply-To: <87wu11w1e3.fsf@gmx.de>
Hi Michael,
> > this is not broken SDP. They use UUID32 which is fine, but actually not
> > quite the normal way.
> >
> > What libs and utils versions are you using?
>
> magdalene:~> uname -a
> Linux magdalene 2.6.7-mh1 #1 Sun Jul 4 11:32:11 CEST 2004 i686 GNU/Linux
>
> magdalene:~> apt-cache policy bluez-cups bluez-utils libbluetooth1
> bluez-cups:
> Installed: 2.8-1
> bluez-utils:
> Installed: 2.8-1
> libbluetooth1:
> Installed: 2.8-1
so everything is as new as possible. Seems we must fix the code to work
correct with UUID32. Where do you got this printer adapter? Looks like I
have to buy one of them or is there a sponsor out there?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-07-18 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-18 17:30 [Bluez-users] Printer adapter w/o SDP Michael Albinus
2004-07-18 19:21 ` Marcel Holtmann
2004-07-18 19:39 ` Michael Albinus
2004-07-18 20:01 ` Marcel Holtmann [this message]
2004-07-19 13:19 ` Michael Albinus
2004-07-25 17:31 ` Marcel Holtmann
2004-07-26 8:56 ` Michael Albinus
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=1090180872.4400.36.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=michael.albinus@gmx.de \
/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