public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: DVornheder@t-online.de (Dirk Vornheder)
To: Marcel Holtmann <marcel@holtmann.org>
Cc: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Some questions
Date: Tue, 15 Jun 2004 22:23:33 +0200	[thread overview]
Message-ID: <200406152223.33329.dvornheder@t-online.de> (raw)
In-Reply-To: <1086863592.1607.47.camel@pegasus>



> > 	00:04:0E:85:35:15	Bluetooth ISDN Access Point
> > 	00:04:0E:83:3C:40	BlueZ (0)
> >                            00:02:72:44:CF:9F
> > BELKIN_PRT_44CF9F
> >
> > My questions:
> >
> > - No driver is loaded after plugin the adapter.
> >
> >    Is this ok ?
>
> I think the hci_usb is loaded, otherwise your device won't work.
>
> > - How can i open a internet connection ?
>
> Use pppd and the CAPI plugin for it. Check with capiinfo for your ISDN
> access point.
>

After loading the capi module the internet connection works.

>
> > - How can i print on my usb printer which is connected to the
> > BELKIN_PRT_44CF9F
> >
> >    bluetooth adapter ?
>
> First send me some info about this printer adapter for my list. The
> output "hcitool info ..." will be nice.
>

Here are the info:

hcitool info 00:02:72:44:CF:9F
Requesting information ...
        BD Address:  00:02:72:44:CF:9F
        Device Name: BELKIN_PRT_44CF9F
        LMP Version: 1.1 (0x1) LMP Subversion: 0x20d
        Manufacturer: Cambridge Silicon Radio (10)
        Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
                <3-slot packets> <5-slot packets> <encryption> <slot offset>
                <timing accuracy> <role switch> <hold mode> <sniff mode>
                <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
                <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
                <power control> <transparent SCO>


> The CUPS printing backend for Bluetooth will help you out here.
>

After compile and install i try to print via spp and hcrp.

A connection to printer adpater is coming up but nothing is printed.

Here are some lines from my /etc/bluetooth/printers.conf:

default {
        # Bluetooth address of the device
        device 00:02:72:44:CF:9F;

        # Bluetooth printing protocol
        protocol serial;
        
        # RFCOMM channel for the connection
        channel 1;

        # Description of the connection
        comment "HP-Deskjet 960C";

The entires in  cups are:

bluetooth://00027244CF9F/spp

Under WIN-XP i can print via hcrp without any problem.

Dirk

  reply	other threads:[~2004-06-15 20:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  6:53 [Bluez-users] Some questions DVornheder
2004-06-10 10:33 ` Marcel Holtmann
2004-06-15 20:23   ` Dirk Vornheder [this message]
2004-06-15 22:38     ` Marcel Holtmann
     [not found]       ` <200406221724.44949.dvornheder@t-online.de>
2004-06-22 21:27         ` Marcel Holtmann
     [not found]           ` <200406231941.04587.dvornheder@t-online.de>
2004-06-23 18:03             ` Marcel Holtmann
     [not found]               ` <200406240756.18537.dvornheder@t-online.de>
2004-06-24 11:21                 ` Marcel Holtmann

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=200406152223.33329.dvornheder@t-online.de \
    --to=dvornheder@t-online.de \
    --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