All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: nicolas <n1c0l4s.l3@wanadoo.fr>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: inactivity of my Bt
Date: Thu, 24 Jun 2004 22:54:24 +0200	[thread overview]
Message-ID: <1088110463.3712.1.camel@pegasus> (raw)
In-Reply-To: <200406242245.43321.n1c0l4s.l3@wanadoo.fr>

Hi Nicolas,

> hciconfig -a gives me:
> 
> # hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:50:F2:7E:3B:3F ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN INQUIRY
>         RX bytes:457793 acl:30836 sco:0 events:1508 errors:0
>         TX bytes:4377 acl:101 sco:0 commands:230 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: RSWITCH HOLD SNIFF PARK
>         Link mode: SLAVE ACCEPT
>         Name: 'BlueZ (0)'
>         Class: 0x000100
>         Service Classes: Unspecified
>         Device Class: Computer, Uncategorized
>         HCI Ver: 1.1 (0x1) HCI Rev: 0x1f9 LMP Ver: 1.1 (0x1) LMP Subver: 0x1f9
>         Manufacturer: Cambridge Silicon Radio (10)

your link policy looks fine. Everything should work as expected. Check
the syslog and run "hcidump -x" as root if you wann know what is going
on.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      parent reply	other threads:[~2004-06-24 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200406232055.06709.n1c0l4s.l3@wanadoo.fr>
     [not found] ` <1088028819.4296.7.camel@pegasus>
2004-06-23 22:28   ` inactivity of my Bt nicolas
2004-06-23 22:23     ` [Bluez-devel] " Marcel Holtmann
2004-06-23 22:47       ` nicolas
2004-06-23 22:50       ` nicolas
2004-06-23 22:46         ` Marcel Holtmann
2004-06-24 17:32           ` nicolas
2004-06-24 17:32             ` Marcel Holtmann
2004-06-24 18:15               ` nicolas
2004-06-24 19:56                 ` Marcel Holtmann
2004-06-24 20:35                   ` nicolas
2004-06-24 20:35                     ` Marcel Holtmann
     [not found]                       ` <200406242245.43321.n1c0l4s.l3@wanadoo.fr>
2004-06-24 20:54                         ` Marcel Holtmann [this message]

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=1088110463.3712.1.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=n1c0l4s.l3@wanadoo.fr \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.