From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] package/rtl8821au: add patch fixing sprintf error
Date: Sun, 2 Aug 2020 12:57:58 +0200 [thread overview]
Message-ID: <20200802125758.3ce2215d@gmx.net> (raw)
In-Reply-To: <CA+h8R2oApXa_RjDPxNXK65S6SNZXgyXvBnEBUy3RuR9BZA=xNQ@mail.gmail.com>
Hello Christian,
On Sat, 1 Aug 2020 17:33:48 -0700, Christian Stewart <christian@paral.in> wrote:
> Hi Peter,
>
> On Sat, Aug 1, 2020 at 2:51 PM Christian Stewart <christian@paral.in> wrote:
> >
> > Hi Peter,
> >
> >
> > On Sat, Aug 1, 2020, 2:34 PM Peter Seiderer <ps.report@gmx.net> wrote:
> >>
> >> maybe its worth to try some other 'upstream' sources, e.g. as
> >> openSUSE [4] does (mentioning previous [5] and [6]), or the first
> >> google search result [7] (did not find the time to dig into the
> >> different repositories to find out which one is the best)...
> >
> >
> > We've been through a number of these over the years. I would not recommend switching to another unless there's a specific reason. As far as I know the current configuration/upstream works fine with USB RTL cards.
Did only a quick test some weeks ago, trying the IBSS mode and to get wifibroadcast
to work (both did not work out as far as I remember, so switched to some other cards)...
>
> See: https://github.com/paralin/buildroot/commit/af8d30846e71e378fdcdb632bbbbfe0aaf7bb669
>
Will take a look at it (if I find some spare time ;-)) and try it out....
Regards,
Peter
> Just out of curiosity I made a patch switching to the aircrack fork,
> but there were some errors at the install step, for example:
>
> depmod: WARNING: /target/lib/modules/4.14.180/extra/88XXau.ko needs
> unknown symbol cfg80211_unlink_bss
> depmod: WARNING: /target/lib/modules/4.14.180/extra/88XXau.ko needs
> unknown symbol ieee80211
>
> Even though the CFG80211 options are enabled in the kernel, and the
> build passes with the old fork.
>
> Maybe there are some path issues going on there.
>
> Looks like the aircrack fork may have better support for packet injection?
>
> Best,
> Christian
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2020-08-02 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 20:37 [Buildroot] [PATCH v1 1/1] package/rtl8821au: add patch fixing sprintf error Christian Stewart
2020-08-01 21:17 ` Thomas Petazzoni
2020-08-01 21:34 ` Peter Seiderer
2020-08-01 21:40 ` Peter Seiderer
2020-08-01 21:43 ` Christian Stewart
2020-08-02 10:51 ` Peter Seiderer
2020-08-01 21:51 ` Christian Stewart
2020-08-02 0:33 ` Christian Stewart
2020-08-02 10:57 ` Peter Seiderer [this message]
2020-08-02 16:00 ` Christian Stewart
2020-10-25 10:00 ` Peter Seiderer
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=20200802125758.3ce2215d@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/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