mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Bastian Germann <bage@debian.org>,
	Vasily Khoruzhick <anarsoul@gmail.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	BlueZ <linux-bluetooth@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [PATCH v4 2/2] Bluetooth: btrtl: add support for the RTL8723CS
Date: Thu, 9 Feb 2023 08:02:06 +0100	[thread overview]
Message-ID: <0B0EFD39-825F-4635-A7F3-CA96BCFED9A2@holtmann.org> (raw)
In-Reply-To: <CABBYNZKnt5=dar6Rmav=Tv3QH1ghSUV2osZPnp7OQLcANp_1Tw@mail.gmail.com>

Hi Luiz,

>> The Realtek RTL8723CS is a SDIO WiFi chip. It also contains a Bluetooth
>> module which is connected via UART to the host.
>> 
>> It shares lmp subversion with 8703B, so Realtek's userspace
>> initialization tool (rtk_hciattach) differentiates varieties of RTL8723CS
>> (CG, VF, XX) with RTL8703B using vendor's command to read the chip type.
> 
> Don't remember anything called rtk_hciattach, besides if that is based
> on hciattach that is already deprecated in favor of btattach.

and btattach is also deprecated. Write a proper serdev based driver.

The hci_ldisc line discipline crap needs to be removed.

Regards

Marcel


  reply	other threads:[~2023-02-09  7:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 15:52 [PATCH v4 0/2] " Bastian Germann
2023-02-08 15:52 ` [PATCH v4 1/2] Bluetooth: Add new quirk for broken local ext features page 2 Bastian Germann
2023-02-08 15:52 ` [PATCH v4 2/2] Bluetooth: btrtl: add support for the RTL8723CS Bastian Germann
2023-02-08 19:37   ` Luiz Augusto von Dentz
2023-02-09  7:02     ` Marcel Holtmann [this message]
2023-02-09  7:14       ` Vasily Khoruzhick

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=0B0EFD39-825F-4635-A7F3-CA96BCFED9A2@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=anarsoul@gmail.com \
    --cc=bage@debian.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=netdev@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®