From: Hin-Tak Leung <hintak_leung@yahoo.co.uk>
To: Herton Ronaldo Krzesinski <herton@mandriva.com.br>
Cc: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org,
John W Linville <linville@tuxdriver.com>,
Johannes Berg <johannes@sipsolutions.net>,
Michael Wu <flamingice@sourmilk.net>,
Andrea Merello <andrea.merello@gmail.com>
Subject: Re: [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B
Date: Wed, 05 Nov 2008 17:11:40 +0000 [thread overview]
Message-ID: <4911D3CC.1050900@yahoo.co.uk> (raw)
In-Reply-To: <200811051342.05303.herton@mandriva.com.br>
Herton Ronaldo Krzesinski wrote:
>> and applying the two patches on top, they applies cleanly and compile okay
>> except for some warnings in a different module about missing symbols
>> (<something>_sta) but the result dies very painfully with a kernel oops:
>
> Looks like something bad in combination of compat-wireless plus kernel
> 2.6.27.4-73.fc10.x86_64, please try a plain wireless-testing tree with the
> two patches.
Hmm, I'll have to check, but I was a bit puzzled that compat-wireless didn't
build the mac80211 module and the fc10 kernel didn't have one either. (and early
kernels have a mac80211.ko). Has this been made obsolete, or did the fc10 kernel
shipped it compiled-in and for some good/bad reason compat-wireless doesn't
build modules that are compiled in? (obviously there is no point in building a
module the older version of which is compiled in since it won't be used...)
The status.retry_count vs status.rate[0].count change must be in mac80211.ko
or some other more generic module?
Hin-Tak
P.S. I know building a whole wireless-testing kernel is the way to go, but
it takes *very long*...
next prev parent reply other threads:[~2008-11-05 17:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 2:02 [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Hin-Tak Leung
2008-11-05 15:42 ` Herton Ronaldo Krzesinski
2008-11-05 17:11 ` Hin-Tak Leung [this message]
2008-11-05 21:36 ` Herton Ronaldo Krzesinski
2008-11-05 22:05 ` Hin-Tak Leung
2008-11-05 22:43 ` Luis R. Rodriguez
2008-11-05 23:16 ` Hin-Tak Leung
2008-11-05 23:35 ` Luis R. Rodriguez
2008-11-06 14:14 ` John W. Linville
2008-11-06 18:53 ` Luis R. Rodriguez
2008-11-06 0:00 ` Hin-Tak Leung
2008-11-06 0:18 ` Larry Finger
2008-11-06 1:02 ` Hin-Tak Leung
2008-11-06 1:36 ` Hin-Tak Leung
2008-11-06 1:42 ` Larry Finger
2008-11-06 4:23 ` Hin-Tak Leung
2008-11-06 20:49 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2008-11-04 13:50 [RFC/RFT PATCH 0/2 v2] rtl8187: implement conf_tx callback/correctly ack tx pkts Herton Ronaldo Krzesinski
2008-11-04 13:50 ` [RFC/RFT PATCH v2 2/2] rtl8187: feedback transmitted packets using tx close descriptor for 8187B Herton Ronaldo Krzesinski
2008-11-04 20:27 ` Hin-Tak Leung
2008-11-04 21:30 ` Herton Ronaldo Krzesinski
2008-11-04 22:31 ` Larry Finger
2008-11-05 11:29 ` Johannes Berg
2008-11-05 15:38 ` Herton Ronaldo Krzesinski
2008-11-05 15:40 ` Johannes Berg
2008-11-05 15:59 ` Herton Ronaldo Krzesinski
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=4911D3CC.1050900@yahoo.co.uk \
--to=hintak_leung@yahoo.co.uk \
--cc=Larry.Finger@lwfinger.net \
--cc=andrea.merello@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=herton@mandriva.com.br \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).