On 26.09.2022 17:29, Hans Petter Selasky wrote:
I've got a supposedly "broken" if_ure dongle from Alexander, but I'm
unable to reproduce the if_ure hang on two different pieces of XHCI
hardware, Intel based and AMD based, which I've got.
This leads me to believe there is a bug in the XHCI driv
On Mon, 26 Sep 2022, Hans Petter Selasky wrote:
On 9/26/22 21:28, Alexander Motin wrote:
Ivan,
On 26.09.2022 13:11, Ivan Quitschal wrote:
bad news im afraid, problem occurred at the first attempt on
speedtest.net.
and I'm really trying to help you analizying this code here myself, but
prob
> -Mensagem original-
> De: Hans Petter Selasky
> Enviada em: segunda-feira, 26 de setembro de 2022 18:29
> Para: Alexander Motin ; Ivan Quitschal
>
> Cc: freebsd-current@freebsd.org; freebsd-...@freebsd.org
> Assunto: Re: RES: TP-LINK USB no carrier after speed test
>
> On 9/26/22 21:
On 9/26/22 21:28, Alexander Motin wrote:
Ivan,
On 26.09.2022 13:11, Ivan Quitschal wrote:
bad news im afraid, problem occurred at the first attempt on
speedtest.net.
and I'm really trying to help you analizying this code here myself,
but problem is: im far from expert on network protocol busin
Ivan,
On 26.09.2022 13:11, Ivan Quitschal wrote:
bad news im afraid, problem occurred at the first attempt on speedtest.net.
and I'm really trying to help you analizying this code here myself, but
problem is: im far from expert on network protocol business. if it is a
network problem at all. s
On Mon, 26 Sep 2022, Hans Petter Selasky wrote:
Hi Ivan,
Can you revert all if_ure patches, and try this one instead.
--HPS
hi Hans
bad news im afraid, problem occurred at the first attempt on speedtest.net.
and I'm really trying to help you analizying this code here myself, but proble
On 9/23/22 23:43, Hans Petter Selasky wrote:
vpanic() at 0x808f4c84 = vpanic+0x184/frame 0xfe003590e900
panic() at 0x808f4a33 = panic+0x43/frame 0xfe003590e960
sleepq_add() at 0x809521ab = sleepq_add+0x37b/frame
0xfe003590e9b0
_sleep() at 0x80902118 =
On Mon, Sep 26, 2022, 7:54 AM Lev Serebryakov wrote:
> On 26.09.2022 13:03, Dimitry Andric wrote:
>
> > Sure, but if you are compiling without -mavx, why would you want the AVX
> > intrinsics? You cannot use AVX intrinsics anyway, if AVX is not enabled.
>Because autovectorization (generation
Hi Ivan,
Can you revert all if_ure patches, and try this one instead.
--HPSdiff --git a/sys/dev/usb/controller/xhci.c b/sys/dev/usb/controller/xhci.c
index 045be9a40b99..09aefb02687d 100644
--- a/sys/dev/usb/controller/xhci.c
+++ b/sys/dev/usb/controller/xhci.c
@@ -2848,8 +2848,16 @@ xhci_transf
On 26.09.2022 13:03, Dimitry Andric wrote:
Sure, but if you are compiling without -mavx, why would you want the AVX
intrinsics? You cannot use AVX intrinsics anyway, if AVX is not enabled.
Because autovectorization (generation of SSE or AVX instructions by compiler
itself, without intrinsics
Quoting Dimitry Andric (from Mon, 26 Sep 2022
12:03:03 +0200):
Sure, but if you are compiling without -mavx, why would you want the AVX
intrinsics? You cannot use AVX intrinsics anyway, if AVX is not enabled.
So I don't fully understand the problem this configure scripting is
supposed to sol
On 25 Sep 2022, at 23:38, Christian Weisgerber wrote:
>
> Dimitry Andric:
>
>>> See https://github.com/llvm/llvm-project/commit/e5147f82e1cb
>>>
>>> - Instead of __builtin_ia32_pabsd128 maybe use _mm_abs_epi32
>>> - Instead of __builtin_ia32_pabsd256 maybe use _mm256_abs_epi32
>>
>> I'm wonder
12 matches
Mail list logo