From: Bastien Nocera <hadess@hadess.net>
To: Don Alexander <bluez-dev@roosoft.ltd.uk>,
BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Configuration for a Linux Bluetooth print Server
Date: Tue, 24 Jul 2007 00:32:00 +0100 [thread overview]
Message-ID: <1185233520.3641.85.camel@cookie.hadess.net> (raw)
In-Reply-To: <46988514.9000601@roosoft.ltd.uk>
On Sat, 2007-07-14 at 09:11 +0100, Don Alexander wrote:
> Hi All,
>
> I know it is perhaps breaking etiquette as this really ought to be a
> user issue. But I have to say I cannot find anywhere in the code or in
> the documentation how to achieve the above task. Simply put, should
> we not be able to set up the stack to emulate a Bluetooth enable
> printer and be able to pass print data onto the normal printer
> functions of CUPS etc. ? Now before anyone starts misunderstanding me
> I am NOT talking about printing TO bluetooth printers (using the CUPS
> driver) but printing TO a Linux box that identifies itself as being a
> compatible bluetooth printer. Obviously the advantages of this are
> enormous by converting any CUPS attached printer into being a
> bluetooth enabled one.
>
> So my question are :
>
> 1) Is this feasible to implement a printer class into the Bluez stack
> or it is a userspace problem?
User-space.
> 2) If it is the right thing to do via the stack how would it best be
> implemented?
>
> 3) What extensions/ API's ought we attach to a generic printer class
> so that data can be exported to the normal print subsystem.
You need to implement a full SPP or HCRP server. HCRP is probably
easier, as you would just push everything to the CUPS server as-is.
Both specs are available on the Bluetooth SIG website.
Cheers
--
Bastien Nocera <hadess@hadess.net>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2007-07-23 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 8:11 [Bluez-devel] Configuration for a Linux Bluetooth print Server Don Alexander
2007-07-23 23:32 ` Bastien Nocera [this message]
[not found] <469E8B6E.6050508@uni-mainz.de>
2007-07-19 6:41 ` bluez-dev
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=1185233520.3641.85.camel@cookie.hadess.net \
--to=hadess@hadess.net \
--cc=bluez-dev@roosoft.ltd.uk \
--cc=bluez-devel@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