From: poma <pomidorabelisima@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless <linux-wireless@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: RTL8189ETV
Date: Tue, 1 Sep 2015 13:27:02 +0200 [thread overview]
Message-ID: <55E58B86.8030708@gmail.com> (raw)
In-Reply-To: <55E4C638.7010704@lwfinger.net>
On 31.08.2015 23:25, Larry Finger wrote:
> On 08/31/2015 03:31 PM, poma wrote:
>> On 31.08.2015 19:51, Larry Finger wrote:
>>> On 08/31/2015 12:06 PM, poma wrote:
>>>> On 31.08.2015 18:00, poma wrote:
>>>>>
>>>>> Hi Fi,
>>>>>
>>>>> What is this device, is it supported by
>>>>> https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8189es
>>>>>
>>>>> $ modinfo rtl8189es
>>>>> modinfo: ERROR: Module rtl8189es not found.
>>>>>
>>>>
>>>> or is it supported by
>>>> https://github.com/orangepi-xunlong/linux-sunxi/tree/orangepi-3.4/drivers/net/wireless/rtl8188eu
>>>> https://github.com/lwfinger/rtl8188eu
>>>> as RTL8188ETV is
>>>>
>>>> $ modinfo rtl8188eu
>>>> modinfo: ERROR: Module rtl8188eu not found.
>>>>
>>>>
>>>> However RTL8188ETV is USB 2.0 device,
>>>> eeeeeeeeeeeeeeeeeee not again!
>>>
>>> That last comment does not help.
>>>
>>> If rtl8188eu is not available, that is the fault of your distro, not anything
>>> that driver maintainers can help. That driver is in the staging directory, and
>>> some distros do not include any of those drivers in their kernels.
>>>
>>> eeeeeeeeeeeeeeeeeee not again! Someone posts about a USB device not found, and
>>> they refuse/fail to provide the USB ID. Why, I do not know when the lsusb
>>> command provides this info so easily.
>>>
>>> Larry
>>>
>>>
>>
>>
>> What's the hurry, Larry.
>> Let's see if Hans knows what type of this device is RTL8189ETV.
>>
>> According to what is written here
>> http://linux-sunxi.org/Xunlong_Orange_Pi#Variants
>> http://www.orangepi.org/orangepi2
>> RTL8189ETV, whatever it is, is an integral part of some "O-Pi" variants.
>>
>> About rtl8188etv can be read here
>> http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=25&highlight=wifi
>> but there is no mention of RTL8189ETV.
>>
>> WikiDevi also returns nothing
>> https://wikidevi.com/wiki/Main_Page
>> "Search results
>> ...
>> There were no results matching the query.
>>
>> Create the page "RTL8189ETV" on this wiki!"
>>
>> I'm trying to determine in advance,
>> what components are supported,
>> what components are not supported,
>> what components will never be supported,
>> what components will never be supported in mainline kernel.
>>
>> Therefore, I can not show 'lsusb' output. :)
>>
>> "Distro" is not decisive in this matter, moreover dunno what are you referring with "your distro".
>>
>> eeeeeeeeeeeeeeeeeeeeee not again!
>
> Silly me. I thought you were trying to get help implemetiing that device.
>
>
Implemetiing!? :)
You must have me confused with someone else, man.
next prev parent reply other threads:[~2015-09-01 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 16:00 RTL8189ETV poma
2015-08-31 17:06 ` RTL8189ETV poma
2015-08-31 17:51 ` RTL8189ETV Larry Finger
2015-08-31 20:31 ` RTL8189ETV poma
2015-08-31 21:25 ` RTL8189ETV Larry Finger
2015-09-01 11:27 ` poma [this message]
2015-09-01 8:43 ` RTL8189ETV Hans de Goede
2015-09-01 11:16 ` RTL8189ETV poma
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=55E58B86.8030708@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=hdegoede@redhat.com \
--cc=linux-wireless@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;
as well as URLs for NNTP newsgroup(s).