public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Power control for EDR
Date: Fri, 08 Jul 2005 01:43:20 +0200	[thread overview]
Message-ID: <1120779800.18553.61.camel@pegasus> (raw)
In-Reply-To: <20050707223942.12A0D464@arbetsmyra.dyndns.org>

Hi Ronny,

> I'm currently implementing transmitter power control for CSR chipsets. 
> I've manged to succed with BlueCore2 and has moved on to BlueCore4 with 
> BT v2.0 and EDR. This one is much trickier though, especially since I'm 
> lacking documentation. 
> 
> Marcel, do you (or any one else for that matter) have information about 
> the pskey and bccmd constants PSKEY_LC_ENHANCED_POWER_TABLE and 
> LIMIT_EDR_POWER? I've seen them mentioned as text only, without the 
> corresponding necessary value.  :(  Perhaps they can be looked up in 
> the development utils PSTool or BTCli? Unfortunately I don't have any 
> of those.

I have no further information about these things. Actually I wasn't
aware of that they exists.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2005-07-07 23:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 22:39 [Bluez-devel] Power control for EDR Ronny L Nilsson
2005-07-07 23:43 ` 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=1120779800.18553.61.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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