All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Jeff Sutherland <jeffs@fairwayacademy.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Timeout message from kernel
Date: Sat, 14 Feb 2004 00:40:29 +0100	[thread overview]
Message-ID: <1076715629.18588.103.camel@pegasus> (raw)
In-Reply-To: <200402131819.10939.jeffs@fairwayacademy.org>

Hi Jeff,

> Making ColdFire the l2test listener seems to work ok:
> /> l2test -r
> l2test[25]: Waiting for connection on psm 10 ...
> l2test[25]: Connect from 00:0A:4F:00:09:5E [imtu 672, omtu 672, flush_to 
> 65535]
>                                                                                 
> l2test[25]: Receiving ...
> l2test[25]: 672 bytes in 0.04 sec, 17.70 kB/s
> l2test[25]: 672 bytes in 0.01 sec, 50.86 kB/s
> l2test[25]: 672 bytes in 0.03 sec, 20.72 kB/s
> 
> and so on and so forth.  Making ColdFire the sender however produces this 
> output on the pc side:
> 
> [root@Arwen test]# ./l2test -r
> l2test[30292]: Waiting for connection on psm 10 ...
> l2test[30293]: Connect from 00:0A:4F:00:13:5F [imtu 672, omtu 672, flush_to 
> 65535]
> l2test[30293]: Receiving ...
> l2test[30293]: 672 bytes in 0.06 sec, 11.28 kB/s
> l2test[30293]: seq missmatch: 1 -> 4
> l2test[30293]: 672 bytes in 0.09 sec, 7.70 kB/s
> l2test[30293]: seq missmatch: 5 -> 8
> l2test[30293]: 672 bytes in 0.08 sec, 8.21 kB/s
> l2test[30293]: seq missmatch: 9 -> 12
> etc., etc.

should not happen. I don't why it happens to you.

> > Maybe this is a role switch problem. Show us both outputs from
> > "hciconfig -a".
> 
> ColdFire:
> /> hciconfig -a
> hci0:   Type: UART
>         BD Address: 00:0A:4F:00:13:5F ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:306 acl:0 sco:0 events:14 errors:0
>         TX bytes:513 acl:0 sco:0 commands:12 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: 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: 0x175 LMP Ver: 1.1 (0x1) LMP Subver: 0x175
>         Manufacturer: Cambridge Silicon Radio (10)
> 
> PC:
> [root@Arwen test]# hciconfig -a
> hci0:   Type: USB
>         BD Address: 00:0A:4F:00:09:5E ACL MTU: 192:8  SCO MTU: 64:8
>         UP RUNNING PSCAN ISCAN
>         RX bytes:1887092 acl:3025 sco:29743 events:1513 errors:0
>         TX bytes:309425 acl:1448 sco:1709 commands:109 errors:0
>         Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
>         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>         Link policy: 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: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
>         Manufacturer: Cambridge Silicon Radio (10)

Both look fine, but you should enable role switch support in hcid.conf
or set it by hand with hciconfig.

> Other than that sequence problem it looks like the link mostly works, still 
> issues with most of the commands of hcitool though, on Coldfire.

Keep trying and look with hcidump at it, but we can also have a bug in
our tools if they are used on a ColdFire processor.

Regards

Marcel




-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-02-13 23:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-12 21:36 [Bluez-users] Timeout message from kernel Jeff Sutherland
2004-02-13  0:14 ` Marcel Holtmann
2004-02-13 14:17   ` Jeff Sutherland
2004-02-13 14:22     ` Marcel Holtmann
2004-02-13 15:23       ` Jeff Sutherland
2004-02-13 15:28         ` Marcel Holtmann
2004-02-13 23:19           ` Jeff Sutherland
2004-02-13 23:40             ` Marcel Holtmann [this message]
2004-02-13 23:58               ` Jeff Sutherland
2004-02-14  0:06                 ` Marcel Holtmann
2004-02-14  4:10                   ` Jeff Sutherland
2004-02-14  8:53                     ` Marcel Holtmann
2004-02-14 13:59                       ` Jeff Sutherland
2004-02-14 15:02                         ` Marcel Holtmann
2004-02-15 22:43                           ` Jeff Sutherland
2004-02-15 23:36                             ` 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=1076715629.18588.103.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=jeffs@fairwayacademy.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 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.