Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://ap.samueldr.com/objects/f1ea0b75-638d-4c1b-b8ab-ed09c0c54059">samueldr (samueldr@ap.samueldr.com)'s status on Tuesday, 21-Jan-2025 05:53:44 JST</a><a href="https://ap.samueldr.com/users/samueldr" title="samueldr@ap.samueldr.com"><img src="https://gnusocial.jp/avatar/153403-48-20230726014827.webp" width="48" height="48" alt="samueldr" style="position: absolute; left: 0; top: 0;">samueldr</a><div><a href="https://fosstodon.org/@awai/113862491281293397" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/159598" title="awai@fosstodon.org">A-wai :debian:</a></li><li><a href="https://gnusocial.jp/user/319436" title="liberux@mastodon.social">Liberux</a></li></ul></div></section><article><p><a href="https://fosstodon.org/@awai">@awai</a> <a href="https://fosstodon.org/@linmob">@linmob</a> <a href="https://mastodon.social/@Liberux">@Liberux</a> Huh... I didn't know. </p><p>The first PinePhone Pro revision staff with AP6256, the second rev and upcoming production all use AW-CM256SM.</p><p>Which I guess explains why it didn't register with me at first. Though I suspect the actual chipset in use differs between CYW43455 and AP6256... So I won't make a judgement call based on that.</p><p>Though quickly searching for WPA3 and pinephone pro, it looks like it also had issues with WPA3 🤔. (I suspect those reports are coming from AW-CM256SM models...)</p><p>But if it's at least not worse than my experience with the AP6256, it should be serviceable for Wi-Fi, and not a drawback for most use-cases at first. Good, I guess.</p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/4412560#notice-8632686">In conversation</a><time datetime="2025-01-21T05:53:44+09:00" title="Tuesday, 21-Jan-2025 05:53:44 JST">about 10 days ago</time> <span>from <span><a href="https://ap.samueldr.com/objects/f1ea0b75-638d-4c1b-b8ab-ed09c0c54059" rel="external" title="Sent from ap.samueldr.com via ActivityPub">ap.samueldr.com</a></span></span><a href="https://ap.samueldr.com/objects/f1ea0b75-638d-4c1b-b8ab-ed09c0c54059">permalink</a></footer></blockquote>

Corresponding Notice

Embed this notice
samueldr (samueldr@ap.samueldr.com)'s status on Tuesday, 21-Jan-2025 05:53:44 JSTsamueldr
in reply to
@awai @linmob @Liberux Huh... I didn't know.
The first PinePhone Pro revision staff with AP6256, the second rev and upcoming production all use AW-CM256SM.
Which I guess explains why it didn't register with me at first. Though I suspect the actual chipset in use differs between CYW43455 and AP6256... So I won't make a judgement call based on that.
Though quickly searching for WPA3 and pinephone pro, it looks like it also had issues with WPA3 🤔. (I suspect those reports are coming from AW-CM256SM models...)
But if it's at least not worse than my experience with the AP6256, it should be serviceable for Wi-Fi, and not a drawback for most use-cases at first. Good, I guess.
In conversationabout 10 days ago from ap.samueldr.compermalink

Public

Embed Notice

HTML Code

Corresponding Notice