On Mon, Jun 8, 2015 at 10:40 PM, Alexis Green <agreen@xxxxxxxxxxxx> wrote:
>
> You should build mac80211 as module instead of built-in driver and
> "make modules" instead of full make. This way you'll be just
> rebuilding mac80211.ko instead of the whole thing.
>
> On Mon, Jun 8, 2015 at 2:39 AM, Duy Tai Nguyen <duytai.cse@xxxxxxxxx> wrote:
> > Hi,
> >
> > I want to inject particular data into beacon frame in Android device.
> > I found two approaches:
> > 1. Write loadable kernel module.
> > 2. Modify MAC80211 subsystem
> > In the first approach, I found that I could not include directly
> > source code from MAC80211 sub system in folder /net/mac80211/. Thus, I
> > used the second approach, but, every time I change any line of source
> > code, it takes 30 minutes to build zImage then install new kernel in
> > my Android device. Finally, I was stuck.
> > Therefore, my questions are:
> > 1. Is it right approach to modify MAC80211 subsystem?
> > 2. Are there any faster approach to modify MAC80211 and test source code?
> > 3. I am curious about the way you write code and test MAC80211. Could
> > you explain in details?
The way i do it is, as below:
1) First time compile the full kernel. With mac80211=m
2) Next time: after changing source :
make modules M=net/mac80211
make modules_install M=net/mac80211
modprobe -v mac80211 -r
modprobe -v mac80211
3) I normally use mac80211_hwsim to test the mac80211 code.
Refer: https://wireless.wiki.kernel.org/en/users/drivers/mac80211_hwsim
In that case:
modprobe -v mac80211_hwsim -r
modprobe -v mac80211_hwsim
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
