From: sagasola uyeoldum <sagasolauyeoldum@yahoo.com>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] bluez nap problems
Date: Tue, 7 Dec 2004 12:29:28 -0800 (PST) [thread overview]
Message-ID: <20041207202928.756.qmail@web52005.mail.yahoo.com> (raw)
In-Reply-To: <1102447685.8447.50.camel@pegasus>
Thank you
I think I messed with the configuration files while
trying to get it up. That solved everything.
--- Marcel Holtmann <marcel@holtmann.org> wrote:
> Hi,
>
> > Ok here it goes:
> >
> > NAP hciconfig -a:
> >
> > hci0: Type: USB
> > BD Address: 00:02:72:03:D3:F2 ACL MTU:
> 192:8
> > SCO MTU: 64:8
> > UP RUNNING PSCAN ISCAN
> > RX bytes:1591 acl:0 sco:0 events:162
> errors:0
> > TX bytes:1302 acl:0 sco:0 commands:70
> 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: ACCEPT MASTER
> > Name: 'BlueZ (0)'
> > Class: 0x000100
> > Service Classes: Unspecified
> > Device Class: Computer, Uncategorized
> > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver:
> 1.1
> > (0x1) LMP Subver: 0x20d
> > Manufacturer: Cambridge Silicon Radio (10)
> >
> > PANU hciconfig -a:
> >
> > hci0: Type: USB
> > BD Address: 00:0D:18:01:19:3B ACL MTU:
> 192:8
> > SCO MTU: 64:8
> > UP RUNNING PSCAN ISCAN INQUIRY
> > RX bytes:122 acl:0 sco:0 events:15
> errors:0
> > TX bytes:304 acl:0 sco:0 commands:13
> 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: ACCEPT MASTER
> > Name: 'miniscule-0'
> > Class: 0x000100
> > Service Classes: Unspecified
> > Device Class: Computer, Uncategorized
> > HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver:
> 1.1
> > (0x1) LMP Subver: 0x36f
> > Manufacturer: Cambridge Silicon Radio (10)
>
> how should this work if both sides are fighting for
> the master role? You
> changed default settings without understanding what
> they mean. Use the
> default hcid.conf.
>
> 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
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
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
prev parent reply other threads:[~2004-12-07 20:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-06 20:01 [Bluez-users] bluez nap problems sagasola uyeoldum
2004-12-06 20:16 ` Marcel Holtmann
2004-12-07 17:32 ` sagasola uyeoldum
2004-12-07 19:28 ` Marcel Holtmann
2004-12-07 20:29 ` sagasola uyeoldum [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=20041207202928.756.qmail@web52005.mail.yahoo.com \
--to=sagasolauyeoldum@yahoo.com \
--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