It seems you are already pissed off, but could you please reply inline
instead of top posting. Its a drag to scroll up and down.
On 4/12/2018 7:05 PM, solsTiCe d'Hiver wrote:
Hi.
I thought I made myself clear.
I leave in France. My system(s) is/are set up to use FR as default
regulatory domain
On 4/12/2018 5:52 PM, Dan Williams wrote:
On Thu, 2018-04-12 at 08:18 -0700, Steve deRosier wrote:
On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel
wrote:
On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote:
Hi.
This is beyond my comprehension that you could assert this is a
non issue.
Well.
On Thu, Apr 12, 2018 at 10:25 AM, solsTiCe d'Hiver
wrote:
> It's the second time that you (Ben and Steve) are implying that I
> might break the law.
>
No implication intended. All I said is regulatory operation is
constrained by laws in various jurisdictions. And how the unit behaves
is likely si
On 04/12/2018 10:25 AM, solsTiCe d'Hiver wrote:
It's the second time that you (Ben and Steve) are implying that I
might break the law.
But why are you saying that ? I am not gonna repeat myself again.
If you force the NIC to use a different regulatory domain that what it
originally was tested
It's the second time that you (Ben and Steve) are implying that I
might break the law.
But why are you saying that ? I am not gonna repeat myself again.
And for the patch, it is also implied that I am able to write one.
2018-04-12 19:11 GMT+02:00 Ben Greear :
> On 04/12/2018 10:05 AM, solsTiCe d
On 04/12/2018 10:05 AM, solsTiCe d'Hiver wrote:
Hi.
I thought I made myself clear.
I leave in France. My system(s) is/are set up to use FR as default
regulatory domain.
But when I plug in that tp-link card, I am restricted to use CN
regulatory domain. Why am I the only one to see this as a prob
Hi.
I thought I made myself clear.
I leave in France. My system(s) is/are set up to use FR as default
regulatory domain.
But when I plug in that tp-link card, I am restricted to use CN
regulatory domain. Why am I the only one to see this as a problem ?
I know that one can only have one regdom de
On Thu, 2018-04-12 at 08:18 -0700, Steve deRosier wrote:
> On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel
> wrote:
> > On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote:
> > >
> > > Hi.
> > >
> > > This is beyond my comprehension that you could assert this is a
> > > non issue.
> >
> >
> > Well
On Thu, Apr 12, 2018 at 3:51 AM, Arend van Spriel
wrote:
> On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote:
>>
>> Hi.
>>
>> This is beyond my comprehension that you could assert this is a non issue.
>
>
> Well. I am just saying that it is by design. There is no way for the
> regulatory code to deter
On 4/12/2018 10:42 AM, solsTiCe d'Hiver wrote:
Hi.
This is beyond my comprehension that you could assert this is a non issue.
Well. I am just saying that it is by design. There is no way for the
regulatory code to determine where you and your hardware actually reside
so instead it takes a co
On 4/12/2018 9:00 AM, solsTiCe d'Hiver wrote:
Nobody cares about this ?
Should I report this as a bug to the LKML ? or elsewhere ? to
ath9k_htc dev ? to crda dev ?
Please.
Hi,
I do not think nobody cares, but what you describe is actually no issue
as far as I can determine. Wifi cards are t
Nobody cares about this ?
Should I report this as a bug to the LKML ? or elsewhere ? to
ath9k_htc dev ? to crda dev ?
Please.
2018-04-10 21:57 GMT+02:00 solsTiCe d'Hiver :
> hi.
>
> I am trying to capture on 2 channels at the same time with 2 cards.
>
> One card is TP-Link TL-W722N v1 using ath9
12 matches
Mail list logo