From: p2p@posteo.de
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: RTL8188S
Date: Tue, 03 Dec 2013 20:14:08 +0100 [thread overview]
Message-ID: <71e5f26b0cd51bcceb26565aa236fe7a@posteo.de> (raw)
In-Reply-To: <1783016.HDzIMuL15q@blech>
Dear Mr. Lamparter,
Am 26.11.2013 21:38 schrieb Christian Lamparter:
> Dear Ms./Mr. ...?
>
> On Tuesday, November 26, 2013 05:47:48 PM p2p@posteo.de wrote:
>> Am 25.11.2013 22:57 schrieb Christian Lamparter:
>> > On Monday, November 25, 2013 06:57:32 PM p2p@posteo.de wrote:
>> >> I have a WLAN dongle with Realtek RTL8188S chip.
>> >> I don't want to use r8712u driver with wext interface
>> >> because I want to establish a wifi direct p2p connection.
>> >
>> > AFICT, you should be able to connect to a p2p-go peer
>> > even if your device (in this case rtl8188s) only supports
>> > station mode...
>> >
>> How do I do this?
> "station mode"!
>
> The theory is: the p2p group owner (go) peer behaves pretty much
> like an Access Point. Hence, legacy devices like the rtl81yySx
> can connect to it the same way like they would connect to an
> accesspoint or router.
>
> No "magic" driver or anything is needed. If you can connect to a
> run-of-the-mill protected AP, you can connect to a running
> wifi-direct
> network.
>
>> >> Unfortunately the original Realtek driver from hp didn't
>> >> work with p2p too.
>> > Why, what happens in this case?
>> >
>>
>> I have downloaded the driver from:
>>
>> http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=48&PFid=48&Level=5&Conn=4&DownTypeID=3&GetDown=false&Downloads=true#RTL8188SU
>
> this would also have worked with r8712u or r92su.
>
>> Installed and loaded the module 8712u.
>>
>> "iw list" doesn't list p2p-client or p2p-go.
>
> "station mode" "station mode" and again "station mode".
>
> "station mode" != "p2p-go" or "p2p-client". Just fire up your peer
> device and let the driver connect (either via WPA2-PSK or WPS). You
> don't need to deal with the console at all, this all can be done
> with the push of a GUI button (NetworkManager, wicd, ...).
>
> Remember: Do it like you simply want to connect to your AP.
> (no p2p magic!)
>
We need the "p2p magic" to develop a linux miracast sink.
>> I followed the thread.
>> It shows me that it makes no sense. I am a beginner and I only can
>> spent time for it if someone tells me for example: fill this module
>> with
>> code for this specific function. I have good literature and I think
>> I
>> can try to help but not lead something.
>
> Hey that's great, that's exactly what needs to be "done". ;-)
>
I don't know yet if I have the time to take part. But as I wrote I have
a good book which describes in detail driver development for 2.6 kernel.
What do you think how many LOC have to been written?
Best regards
p2p
next prev parent reply other threads:[~2013-12-03 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 17:57 RTL8188S p2p
2013-11-25 21:57 ` RTL8188S Christian Lamparter
2013-11-25 22:12 ` RTL8188S Larry Finger
2013-11-25 22:59 ` RTL8188S Christian Lamparter
2013-11-26 16:47 ` RTL8188S p2p
2013-11-26 20:38 ` RTL8188S Christian Lamparter
2013-12-03 19:14 ` p2p [this message]
2013-12-03 20:14 ` RTL8188S Christian Lamparter
[not found] ` <ca7208642ae7c2ad48c990314f2f03ba@posteo.de>
2013-12-04 19:20 ` RTL8188S Christian Lamparter
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=71e5f26b0cd51bcceb26565aa236fe7a@posteo.de \
--to=p2p@posteo.de \
--cc=chunkeey@googlemail.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