Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15071] RTL8723BS library is outdated
Date: Thu, 20 Oct 2022 10:57:38 +0000	[thread overview]
Message-ID: <bug-15071-163-rsoRhNYfiU@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15071-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15071

--- Comment #2 from Giulio Benetti <giulio.benetti@benettiengineering.com> ---
(In reply to alirezatm from comment #0)

Hi,

it's true, package rtl8723bs is outdated and indeed has been dropped with this
commit:
https://git.busybox.net/buildroot/commit/?id=7763ba7007172ceb5e928ae5902735d727aaa90d

As pointed by:
https://github.com/hadess/rtl8723bs/commit/3bb1d33ad98c1d77b5e17a1b707e137b35e6d0a5
now the driver has made it into staging Linux driver folder.

So you can access and configure Linux by issuing:
$ make linux-menuconfig
and then you can find RTL8723BS driver. But take care because it needs some
CONFIG_ to be enabled:
CONFIG_STAGING=y
CONFIG_WLAN=y
CONFIG_MMC=y
CONFIG_CFG80211=y
CONFIG_MODULES=y

To find these informations you can search "rtl8723bs" in linux-menuconfig(as
well as in Buildroot menuconfig) by typing "/" and there it will be shown the
"depends on" and what it "Selects".

This way you should be able to have the driver built.

Best regards

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  parent reply	other threads:[~2022-10-20 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20 10:27 [Buildroot] [Bug 15071] New: RTL8723BS library is outdated bugzilla
2022-10-20 10:30 ` [Buildroot] [Bug 15071] " bugzilla
2022-10-20 10:57 ` bugzilla [this message]
2022-10-30 20:20 ` bugzilla

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=bug-15071-163-rsoRhNYfiU@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@uclibc.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