From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Fisher Grubb <fisher.grubb@gmail.com>
Cc: Xose Vazquez Perez <xose.vazquez@gmail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Realtek USB WiFi rtl8192eu
Date: Tue, 10 May 2016 22:40:21 -0400 [thread overview]
Message-ID: <wrfjbn4diaga.fsf@redhat.com> (raw)
In-Reply-To: <CAD4Xxq8kEf6RJe=LD=uikSeC29RHO--ain0RhDL6976P2Vq=Xw@mail.gmail.com> (Fisher Grubb's message of "Wed, 11 May 2016 11:32:12 +1000")
Fisher Grubb <fisher.grubb@gmail.com> writes:
> Hi Jes,
>
> Thanks for the info.
>
> Ok, so I assume I just Google how to bring/compile a newer
> "unreleased" driver into a previous kernel version.
>
> Do I just need my current kernel's headers and typical GCC build toolchain?
>
> This is for Debian 7.9 on the ARM based BeagleBone Black board (Texas
> Instruments Sitara AM3358 CPU), which I uses kernel v3.8.13-bone79.
>
> I'm asking in case there's a big difference between kernel 3 to 4 for
> this type of driver to be compiled.
>
> I'm pretty sure certain kernel customisations were added by Robert
> Nelson for this board (I think he is quite involved with
> porting/fixing stuff for this board and the raspberry pi) , so I don't
> know how easy it would be for me to use a version 4 kernel.
Bringing back the driver into an older kernel is an open question. No
idea if that will work or not. Also note that ARM support is very
lightly tested and I do not believe anyone tested rtl8192eu support with
ARM.
Note that the driver currently does not support MESH and AP mode.
Jes
next prev parent reply other threads:[~2016-05-11 2:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 12:58 Realtek USB WiFi rtl8192eu Xose Vazquez Perez
2016-05-10 13:01 ` Xose Vazquez Perez
2016-05-10 13:16 ` Fisher Grubb
2016-05-10 20:51 ` Jes Sorensen
2016-05-11 1:32 ` Fisher Grubb
2016-05-11 2:40 ` Jes Sorensen [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-10 12:41 Fisher Grubb
2016-05-10 12:53 ` Fisher Grubb
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=wrfjbn4diaga.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=fisher.grubb@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=xose.vazquez@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.