Devicetree
 help / color / mirror / Atom feed
From: "Diederik de Haas" <diederik@cknow-tech.com>
To: "Diederik de Haas" <diederik@cknow-tech.com>,
	<sashiko-reviews@lists.linux.dev>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>,
	"Heiko Stuebner" <heiko@sntech.de>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/3] arm64: dts: rockchip: Add support for FriendlyElec NanoPC-T6 Plus
Date: Tue, 15 Sep 2026 13:13:45 +0200	[thread overview]
Message-ID: <DLFUGSHJFYH8.1NFX2YZ9J7EMA@cknow-tech.com> (raw)
In-Reply-To: <DL959BBXDOAZ.2RNX9SJVZIKPK@cknow-tech.com>

On Mon Sep 7, 2026 at 4:12 PM CEST, Diederik de Haas wrote:
> I have a MT7925 M.2 Wi-Fi+BT card in my NanoPC-T6 Plus and while
> Wi-Fi looks great (1.4/1.9 Gbps connection), BT has been horrible.
> Similar story for my BE200 M.2 Wi-Fi+BT card I have in my LTS board.
> And the most annoying thing: it's behavior is very inconsistent.

FWIW: that was caused by a broken and a severely damaged pigtail.

> My cheapo (cherry) BT keyboard works fine/decent and connecting to my FNB58 USB
> meter over BT is great. Haven't tried anything useful with that latter one, but
> it consistently finds it and when I connect to it, it succeeds. It even stays
> connected \o/ :-O

And those worked (somewhat) because of close proximity to the chip.

> All the rest? It either doesn't see it, it can't connect to it, or it
> connects to it to drop the connection after a few seconds.
> And after a reboot? No one knows what will happen.

After replacing the pigtails, Wi-Fi works even better and BT works really
good as well.

> I've had ONE time a stable connection between the MT7925 and my BT speakers.
> Only it didn't show as a sink in pipewire/wireplumber so I couldn't actually
> use it. I haven't been able to make a connection since.

Connecting to my BT speaker (thus) works great now too, but it still doesn't
show up as a sink in pipewire. But that's either a driver or a pipewire and/or 
wireplumber issue. HW if fine :-D

Cheers,
  Diederik

      reply	other threads:[~2026-09-15 11:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 12:22 [PATCH 0/3] Add support for FriendlyElec NanoPC-T6 Plus Diederik de Haas
2026-09-07 12:22 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add " Diederik de Haas
2026-09-07 12:22 ` [PATCH 2/3] arm64: dts: rockchip: Move sound cards to board files for NanoPC-T6 Diederik de Haas
2026-09-07 12:22 ` [PATCH 3/3] arm64: dts: rockchip: Add support for FriendlyElec NanoPC-T6 Plus Diederik de Haas
2026-09-07 12:34   ` sashiko-bot
2026-09-07 14:12     ` Diederik de Haas
2026-09-15 11:13       ` Diederik de Haas [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DLFUGSHJFYH8.1NFX2YZ9J7EMA@cknow-tech.com \
    --to=diederik@cknow-tech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox