From nobody Mon Mar 04 22:17:52 2024 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TpY4n39VQz5DPCb for ; Mon, 4 Mar 2024 22:18:49 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com [209.85.208.170]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TpY4m57p6z447J for ; Mon, 4 Mar 2024 22:18:48 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of ccfreebsd@gmail.com designates 209.85.208.170 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lj1-f170.google.com with SMTP id 38308e7fff4ca-2d311081954so57377431fa.2 for ; Mon, 04 Mar 2024 14:18:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709590726; x=1710195526; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bLgTRNbgdIzbPMolDfOcAdPEHCDE2wvYSq+hegLBLiY=; b=mqHfhWWhfKPUvrEeZ4ZW3pChUfj/vxFoK/DvUir1FcYTvqv8H34/Nu1dA5wIIYHjTe UOLcWzwK9qawtapvS+7RIF9t6PyOXUxk7ITf/jp5kNe8DaA0sHqUzVIIunZWESJy1s9X CsGT7F9g2gFUr1qdjulIcj5xB+73RPhYL+ngW1aURHuFFxWEr4rIrtqteaSV/QsPWu6D ecZEjTw/oscDSu0IdRUaZOIlk9/sll9oPn4Vc5ByphI1ZLKiR/IOETe+DyxsHL6B0IO1 uPl3SwDEX8/P1pPrrU3Gai4FxvAEpJo7/2v5sdZuts8KFwqVadkzDZPqgBDjhaq7v881 zlIg== X-Gm-Message-State: AOJu0YzZJ2Q4hlkVZ2S3MobnmnVVZzvjIiPI3C/kbIluCGEvG8MYxixM AGungEFOIXM6oVe8WIGNDoGeRfRtbKmYSbiiZZs5QI8UEzssjQMrNMBK3JEOxIU= X-Google-Smtp-Source: AGHT+IExZBR5xXHKEpPLGzUt35PMGXwBKfbnq1KqzbEvwYfOlX4RCIk9FeXLSS4/lTC2tLSp6mSRLA== X-Received: by 2002:ac2:4c12:0:b0:512:cd8d:9815 with SMTP id t18-20020ac24c12000000b00512cd8d9815mr68307lfq.15.1709590725620; Mon, 04 Mar 2024 14:18:45 -0800 (PST) Received: from mail-lj1-f170.google.com (mail-lj1-f170.google.com. [209.85.208.170]) by smtp.gmail.com with ESMTPSA id i23-20020a056512007700b0051322c11100sm1876680lfo.221.2024.03.04.14.18.29 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 04 Mar 2024 14:18:39 -0800 (PST) Received: by mail-lj1-f170.google.com with SMTP id 38308e7fff4ca-2d28e465655so73308651fa.0 for ; Mon, 04 Mar 2024 14:18:29 -0800 (PST) X-Received: by 2002:ac2:5b4d:0:b0:513:4b49:e1c3 with SMTP id i13-20020ac25b4d000000b005134b49e1c3mr63955lfp.53.1709590708785; Mon, 04 Mar 2024 14:18:28 -0800 (PST) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 From: Cheng Cui Date: Mon, 4 Mar 2024 17:17:52 -0500 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Feb 26 ~ Mar 1) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="000000000000e89b320612dd1aba" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.82 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; NEURAL_HAM_MEDIUM(-0.92)[-0.922]; FORGED_SENDER(0.30)[cc@freebsd.org,ccfreebsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[cc@freebsd.org,ccfreebsd@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.208.170:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.170:received,209.85.208.170:from] X-Rspamd-Queue-Id: 4TpY4m57p6z447J --000000000000e89b320612dd1aba Content-Type: text/plain; charset="UTF-8" During testing the patches of D43634 and D43648, which also solves PR 277095 when enabling `LKPI_80211_HW_CRYPTO`, I found the data path does not work after successful association with the AP. For example, DHCP request does not work. I am adding new debug prints to investigate the issue. 1. Finished testing/reviewing D43944 2. After testing/reviewing, made comments on D43967, D43634 and D43648. These are pending for new updates. 3. Created PR277416, which currently is a low priority with a purpose of adding flag `D80211_TRACE_CRYPTO` for LKPI crypto debugging. -- Best Regards, Cheng Cui --000000000000e89b320612dd1aba Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
During testing the patches of D43634 and D43648, which als= o solves PR=C2=A0277095 when enabling=C2=A0`LKPI_80211_HW_CRYPTO`, I found = the data path does not work after successful association with the AP. For e= xample, DHCP request does not work. I am adding new debug prints to investi= gate the issue.
  1. Finished testing/reviewing=C2=A0D43944
  2. After= testing/reviewing, made comments on D43967, D43634 and D43648. These are p= ending for new updates.
  3. Created=C2=A0PR277416, which currently=C2= =A0is a low priority with a purpose of adding flag=C2=A0`D80211_TRACE_CRYPT= O` for LKPI crypto debugging.

--
Best Regards= ,
Cheng Cui
--000000000000e89b320612dd1aba--