From nobody Mon Apr 08 15:59:34 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 4VCv1q0TQjz5HGMg for ; Mon, 8 Apr 2024 16:00:15 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lj1-f174.google.com (mail-lj1-f174.google.com [209.85.208.174]) (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 4VCv1p2q1vz4J7n for ; Mon, 8 Apr 2024 16:00:14 +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.174 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lj1-f174.google.com with SMTP id 38308e7fff4ca-2d6fc3adaacso58710161fa.2 for ; Mon, 08 Apr 2024 09:00:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712592011; x=1713196811; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=0EOh5YIEdJeN+2bvuFiq0678SRPaGCyrA915qXDFpNs=; b=v5Fe7zU7CmMdau2sNAthj2wwAPl9R7IlBv2oYyH/yOPsiCuXyLm47bIWfPOLCBq+yd DreOnToW59Ys3WptoEs42GMeeEjMQQ9l2AXUlP+Fhw6Cw914ddGeMN86uu7KzG2vCiU/ CocBeQBcGN3D2Dak11m7ZTgIfwcXNZQvC5oUIL+jZPuQ3ExI2oWEQcs537NlvFMUar4f jqvHl3SWdeDsX3PpGVt6fho8EpPJJSDR/4ejWeEJdmlsxYtU7vR6NAtNWefv+jyPrvfb UhVJmeCkPlyg55sIgvcR/r2D1LdmE5D4ykf2ZA+o3xrqHevDAwafSq+PcrNAarzqO8jD INUg== X-Gm-Message-State: AOJu0YwpJAdrytERdoEKKbU5BKLJ/jqBY5lyfmDxDbWeTzxc95MkCeWB Sa79DDaVMn0zTBriHcDwSfI3nZ6L0JV5YbnPIw8YgQ5CjHu/201BDgtVg16RsFo= X-Google-Smtp-Source: AGHT+IFErAMVfTWXsNgw7QhmIF6tKFUH1sw/Jn+zleyoJ58XLOYgEDdxwuTJ7ql2AiW4CTk1Gc/OUA== X-Received: by 2002:a2e:9655:0:b0:2d8:6065:e2b2 with SMTP id z21-20020a2e9655000000b002d86065e2b2mr6026058ljh.46.1712592010856; Mon, 08 Apr 2024 09:00:10 -0700 (PDT) Received: from mail-lj1-f175.google.com (mail-lj1-f175.google.com. [209.85.208.175]) by smtp.gmail.com with ESMTPSA id l25-20020a2e8699000000b002d845ffd60bsm1241819lji.3.2024.04.08.09.00.10 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 08 Apr 2024 09:00:10 -0700 (PDT) Received: by mail-lj1-f175.google.com with SMTP id 38308e7fff4ca-2d6fc3adaacso58709831fa.2 for ; Mon, 08 Apr 2024 09:00:10 -0700 (PDT) X-Received: by 2002:a05:651c:1509:b0:2d8:9487:7588 with SMTP id e9-20020a05651c150900b002d894877588mr2096657ljf.38.1712592010501; Mon, 08 Apr 2024 09:00:10 -0700 (PDT) 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, 8 Apr 2024 11:59:34 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Apr 01 ~ Apr 05) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="0000000000006e7198061597e6cf" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.56 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.67)[-0.666]; FORGED_SENDER(0.30)[cc@freebsd.org,ccfreebsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; 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]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; 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.174:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.208.174:from,209.85.208.175:received] X-Rspamd-Queue-Id: 4VCv1p2q1vz4J7n --0000000000006e7198061597e6cf Content-Type: text/plain; charset="UTF-8" Still working on the HW key/encryption/decryption support under the `LKPI_80211_HW_CRYPTO` block. 1. Firstly, the Linux kernel debugging is more complicated than I thought. For example, the crash(8)/kdump based kernel core file read does not have the gdb frame check on the interested individual frame trace. It looks like kgdb is used for live kernel debugging through the console, or I have not found a reliable source to debug core dump files by using kgdb. This makes me feel I am in favor with the FreeBSD kgdb workflow (it can work on a kernel core file). 2. Secondly, even with the help of printk in Linux and made sure all the necessary parameters are setup correctly for the `struct ieee80211_key_conf` before calling `lkpi_80211_mo_set_key`, as I compared these parameters in the same tx path in Linux, the FreeBSD hw encryption still is not working, and packet capture shows no tx ccmp encryption in the header. In discussion with Bjoern, I may need to focus on the ieee80211_tx_info struct. 3. Updated the tracking PR 277996 with my current investigation. I need to dig up further on the key setup process and the corresponding LinuxKPI code on different flags setup. 4. I still need more feedback on how to proceed with patch D44463 . I have sent a private email to adrian @ asking for help, and I am waiting for his response. Meanwhile, I have sent out an email to olivier@, and asked him about test_ccmp.c in regression tests. I am still waiting for his responses. -- Best Regards, Cheng Cui --0000000000006e7198061597e6cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Still working on the HW key/encryption/decryption support = under the `LKPI_80211_HW_CRYPTO` block.

  1. Firstly,= the Linux kernel debugging is more complicated than I thought. For example= , the crash(8)/kdump based kernel core file read does not have the gdb fram= e check on the interested individual frame trace. It looks like kgdb is use= d for live kernel debugging through the console, or I have not found a reli= able source to debug core dump files by using kgdb. This makes me feel I am= =C2=A0in favor with the FreeBSD kgdb workflow (it can work on a kernel core= file).=C2=A0
  2. Secondly, even with the help of printk in Linux and m= ade sure all the necessary parameters are setup=C2=A0correctly for the `str= uct ieee80211_key_conf` before calling `lkpi_80211_mo_set_key`, as I compar= ed these parameters in the same tx path in Linux, the FreeBSD hw encryption= still is not working, and packet capture shows no tx ccmp encryption in th= e header. In discussion with Bjoern, I may need to focus on the ieee80211_t= x_info struct.
  3. Updated the tracking PR=C2=A0277996=C2=A0with my curre= nt investigation. I need to dig up further on the key setup process and the= corresponding LinuxKPI code on different flags setup.
  4. I still need= more feedback on how to proceed with patch=C2=A0D44463. I have sent = a private email to=C2=A0adrian@ asking for help, and I am waiting = for his response.
Meanwhile, I have sent out an email to=C2= =A0olivier@, and asked him about=C2=A0test_cc= mp.c in regression tests. I am still waiting for his responses.
<= br>
--
Best Regards,
Cheng Cui
--0000000000006e7198061597e6cf--