From: "Han Hoekstra" <Han.Hoekstra@WirelessValue.nl>
To: <bluez-users@lists.sourceforge.net>
Subject: RE: [Bluez-users] Has anyone seen these problems with theCSRBlueCore and BlueZ before ?
Date: Thu, 17 Mar 2005 16:43:42 +0100 [thread overview]
Message-ID: <E1DBxAV-000151-Po@sc8-sf-mx2.sourceforge.net> (raw)
In-Reply-To: <1111071510.11792.88.camel@pegasus>
Hey Marcel,
We are using a Mitsumi WML-C20, which is a BlueCore 02, I believe it is a
BC02-Flash, but I'm not 100% sure about that. I have checked on the CSR
support web-site that I have the latest firmware and that was the case, so
firmware is up to date.
Greetings,
Han
---
Han Hoekstra
Wireless Value B.V.
Waanderweg 30a
7812 HZ Emmen
Tel: +31-591-633200
-----Original Message-----
From: bluez-users-admin@lists.sourceforge.net
[mailto:bluez-users-admin@lists.sourceforge.net] On Behalf Of Marcel
Holtmann
Sent: donderdag 17 maart 2005 15:59
To: BlueZ Mailing List
Subject: RE: [Bluez-users] Has anyone seen these problems with
theCSRBlueCore and BlueZ before ?
Hi Han,
> The info I get from hciconfig -a is :
>
> hci0: Type: UART
> BD Address: 00:A0:96:0A:BF:D4 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:303 acl:0 sco:0 events:13 errors:0
> TX bytes:434 acl:0 sco:0 commands:12 errors:0
> Features: 0xff 0xff 0x8f 0x78 0x18 0x18 0x00 0x80
> 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.2 (0x2) HCI Rev: 0x5df LMP Ver: 1.2 (0x2) LMP Subver:
> 0x5df
> Manufacturer: Cambridge Silicon Radio (10)
>
> This info is what I get just after booting the board.
this is a HCI 18.2 firmware on a BlueCore02 or BlueCore3 chip. What kind of
chip is it? Is it a ROM or External/Flash version?
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-17 15:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-17 13:30 [Bluez-users] Has anyone seen these problems with the CSR BlueCore and BlueZ before ? Han Hoekstra
2005-03-17 14:02 ` Marcel Holtmann
2005-03-17 14:19 ` [Bluez-users] Has anyone seen these problems with the CSRBlueCore " Han Hoekstra
2005-03-17 14:58 ` Marcel Holtmann
2005-03-17 15:43 ` Han Hoekstra [this message]
2005-03-17 15:35 ` [Bluez-users] Has anyone seen these problems with the CSR BlueCore " Erwin Authried
2005-03-17 16:28 ` Steven Singer
2005-03-17 16:50 ` Marcel Holtmann
2005-03-17 17:50 ` Steven Singer
2005-03-17 19:06 ` 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=E1DBxAV-000151-Po@sc8-sf-mx2.sourceforge.net \
--to=han.hoekstra@wirelessvalue.nl \
--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 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.