From: Larry Finger <Larry.Finger@lwfinger.net>
To: Darshan Nandanwar <dk.manit@gmail.com>
Cc: Darshan Kumar NANDANWAR <Darshan.KN@st.com>,
"John W. Linville" <linville@tuxdriver.com>,
wireless <linux-wireless@vger.kernel.org>,
Srikrishna Pramoda ATIKUKKE <srikrishna.pramodaatikukke@st.com>
Subject: Re: insmod RTL8192CE OOPS on 2.6.32.16
Date: Fri, 23 Dec 2011 14:15:30 -0600 [thread overview]
Message-ID: <4EF4E162.5040506@lwfinger.net> (raw)
In-Reply-To: <CAHeY5QcXDdi73nGC5F=-WWHzBzz1W7sj5har4L=_Ah_5xa0yBw@mail.gmail.com>
On 12/23/2011 12:09 PM, Darshan Nandanwar wrote:
> Larry ,
> i am using compat-wireless-2011-12-08.tar.bz2
> <http://linuxwireless.org/download/compat-wireless-2.6/compat-wireless-2011-12-08.tar.bz2>..I
> find the same issue with 8192cU driver as well.. Could you suggest me the commit
> which fixed the issue? i went through your git log , but don't find the issue
> regarding this...
> Once i have the setup ready , i will try to give you debug=4 log .
I'm confused. The 2011-12-08 version of compat-wireless has the patch I sent
yesterday already built in - you should not have needed to apply it. In fact, it
should not have applied to that source.
You would only see the git commit log when you have a full git tree from either
mainline or wireless-testing.
I'm also confused about your statement "I find the same issue with 8192cU driver
as well.". I guess you must mean that the firmware does not load. If so, do you
have firmware loading configured in your kernel?
Larry
prev parent reply other threads:[~2011-12-23 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D6068D304DED1F4FBFC1F56ECFA211D85A1EA7BBF0@EAPEX1MAIL1.st.com>
2011-12-21 14:54 ` insmod RTL8192CE OOPS on 2.6.32.16 Larry Finger
2011-12-21 15:16 ` John W. Linville
2011-12-21 19:38 ` Larry Finger
[not found] ` <D6068D304DED1F4FBFC1F56ECFA211D85A1EA7BE7A@EAPEX1MAIL1.st.com>
2011-12-22 16:06 ` Larry Finger
2011-12-23 9:02 ` Darshan Kumar NANDANWAR
2011-12-23 16:22 ` Larry Finger
[not found] ` <CAHeY5QcXDdi73nGC5F=-WWHzBzz1W7sj5har4L=_Ah_5xa0yBw@mail.gmail.com>
2011-12-23 20:15 ` Larry Finger [this message]
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=4EF4E162.5040506@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Darshan.KN@st.com \
--cc=dk.manit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=srikrishna.pramodaatikukke@st.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).