n as someone from Broadcom QA Testing Team, will find that the
root cause of that issue depends on Linux kernel.
I guess I already did my best to try debugging and solving for *free* a
Broadcom issue which: 1) doesn't depend on me, 2) is locked down in a
proprietary firmware, 3) is protecte
n done any step so far, to root the cause of this issue?
5) Since I have spent money on that device, I would like at least
to monitor the work in progress done to root the cause of this issue -
how can I?
Thanks & Greetings
On Wed, Mar 4, 2015, at 10:01 AM, Arend van Spriel wrote:
> On 03/04
the work in progress done to root the cause of this issue -
how can I?
Thanks Greetings
On Wed, Mar 4, 2015, at 10:01 AM, Arend van Spriel wrote:
On 03/04/15 16:39, Nikita N. wrote:
Dear Arend,
as followup to my last inquiry, since it's passed more than 2 weeks, I'm
afraid I didn't receive any
already did my best to try debugging and solving for *free* a
Broadcom issue which: 1) doesn't depend on me, 2) is locked down in a
proprietary firmware, 3) is protected by secrecy of proprietary Broadcom
informations.
Thanks Greetings.
--
Nikita N.
niki...@operamail.com
On Thu, Mar 5
or any technical datasheet specification document
about BCM4313 on Broadcom website and others.
Did not find any.
Could you please send me a detailed technical datasheet specification
document about BCM4313, for programming/dev purposes?
Thank you & Greetings
On Tue, Feb 17, 2015, at 01:03 AM, N
about BCM4313 on Broadcom website and others.
Did not find any.
Could you please send me a detailed technical datasheet specification
document about BCM4313, for programming/dev purposes?
Thank you Greetings
On Tue, Feb 17, 2015, at 01:03 AM, Nikita N. wrote:
Hi Arend,
brcmsmac does assure tx
Hi Arend,
> brcmsmac does assure tx power is within regulatory limits by enforcing a
> world regulatory domain. So what is not supported is modifying tx power
> settings through user-space.
Yes, I believe that could be right, *a* world regulatory domain looks
indeed enforced, the USA one
Hi Arend,
brcmsmac does assure tx power is within regulatory limits by enforcing a
world regulatory domain. So what is not supported is modifying tx power
settings through user-space.
Yes, I believe that could be right, *a* world regulatory domain looks
indeed enforced, the USA one only,
inux
community, and the unsatisfactory Customers care.
Thanks for your attention.
--
Nikita N.
niki...@operamail.com
On Mon, Feb 16, 2015, at 07:45 AM, Arend van Spriel wrote:
> On 02/16/15 14:53, Nikita N. wrote:
> > Hi Dear brcmsmac Devs,
> > following up my previous email, since I d
n the
table and call wlc_lcnphy_set_target_tx_pwr=40, to get a TX power less
that 19dbm?
4) if it was not correct, or partially correct, what am I missing or
doing wrong, in order to push the TX transceiver power less than 19dbm?
Thanks for your attention.
--
Nikita N.
niki...@operamail.com
On Sun, Feb 15, 2015, a
, and the unsatisfactory Customers care.
Thanks for your attention.
--
Nikita N.
niki...@operamail.com
On Mon, Feb 16, 2015, at 07:45 AM, Arend van Spriel wrote:
On 02/16/15 14:53, Nikita N. wrote:
Hi Dear brcmsmac Devs,
following up my previous email, since I didn't receive any feedback, I
wlc_lcnphy_set_target_tx_pwr=40, to get a TX power less
that 19dbm?
4) if it was not correct, or partially correct, what am I missing or
doing wrong, in order to push the TX transceiver power less than 19dbm?
Thanks for your attention.
--
Nikita N.
niki...@operamail.com
On Sun, Feb 15, 2015, at 05:32 AM
12 matches
Mail list logo
