From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Paul Thomas <pthomas8589@gmail.com>,
linux-wireless@vger.kernel.org,
Andrea Merello <andreamrl@tiscali.it>
Subject: Re: Realtek rtl8188 support?
Date: Thu, 27 May 2010 00:21:26 +0200 [thread overview]
Message-ID: <AANLkTin6cAHj2p266yMLQkrpkhCdX98leNl5F8f3DAJR@mail.gmail.com> (raw)
In-Reply-To: <1274911569.2593.8.camel@mj>
On Thu, May 27, 2010 at 12:06 AM, Pavel Roskin <proski@gnu.org> wrote:
> On Mon, 2010-03-29 at 15:19 -0700, Paul Thomas wrote:
>> OK, I'd love to get to where Pavel & Gabor are, but I think I'm having
>> trouble with the PCI dependency. I'm on an arm platform without PCI
>> (atmel at91sam9g20). If I remove the PCI dependency from the Kconfig
>> it does compile with warnings, and then when the module loads I get
>> "r8192s_usb: Unknown symbol wireless_send_event".
>>
>> I'm happy to hang out and try again when the driver leaves staging,
>> but I thought I might mention the PCI dependency now.
>
> wireless_send_event should be available if WIRELESS_EXT is selected in Kconfig.
>
> But I cannot find the "r8192s_usb" symbol in any staging drivers, so I
> have no idea which driver you are talking about.
r8192s_usb is not a symbol, it is the name of the module being loaded.
>
> I suggest that you don't hijack existing threads to report new issues.
> When reporting a problem, please give the kernel version, the driver
> name and whatever details are needed for others to reproduce the
> problem.
>
>> > CCMP is working, and I could browse the web over it!
>
> Please don't quote parts of the message that are irrelevant to what you
> are saying.
>
> --
> Regards,
> Pavel Roskin
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2010-05-26 22:21 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-06 17:45 Realtek rtl8188 support? Paul Thomas
2010-03-06 18:07 ` Gábor Stefanik
2010-03-07 8:16 ` Pavel Roskin
2010-03-07 15:36 ` Gábor Stefanik
2010-03-10 1:59 ` Pavel Roskin
2010-03-10 3:16 ` Pavel Roskin
2010-03-29 22:19 ` Paul Thomas
2010-03-29 23:32 ` Gábor Stefanik
2010-05-25 0:16 ` Paul Thomas
2010-05-25 23:00 ` Frederic Leroy
2010-05-26 22:06 ` Pavel Roskin
2010-05-26 22:21 ` Gábor Stefanik [this message]
2010-05-28 16:35 ` Pavel Roskin
2010-09-10 11:29 ` Claus Ried
2010-09-18 3:37 ` Hin-Tak Leung
2010-09-18 13:43 ` Stefan Lippers-Hollmann
[not found] ` <AANLkTimz6bR7mLnEgeBzBZrbKC+jp2bx3VTya=YL2KjV@mail.gmail.com>
[not found] ` <201009212120.07914.s.L-H@gmx.de>
2010-10-28 18:26 ` Larry Finger
2010-10-28 21:48 ` Stefan Lippers-Hollmann
2010-10-28 22:10 ` Larry Finger
2010-10-29 20:02 ` Stefan Lippers-Hollmann
2010-10-29 20:03 ` staging: r8712u: Fix external firmware loading Stefan Lippers-Hollmann
2010-10-29 20:26 ` Realtek rtl8188 support? Walter Goldens
2010-10-29 21:27 ` Gábor Stefanik
2010-10-30 4:06 ` Larry Finger
2010-10-30 14:49 ` John W. Linville
2010-10-30 18:11 ` Gábor Stefanik
2010-10-31 3:44 ` Larry Finger
2010-10-31 11:30 ` Walter Goldens
2010-10-31 15:04 ` Larry Finger
2010-12-16 13:25 ` Walter Goldens
2010-12-16 14:10 ` Larry Finger
2011-01-25 7:57 ` Brian Prodoehl
2010-09-18 23:02 ` Paul Thomas
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=AANLkTin6cAHj2p266yMLQkrpkhCdX98leNl5F8f3DAJR@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=andreamrl@tiscali.it \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.org \
--cc=pthomas8589@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 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).