linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Malte Gell <malte.gell@gmx.de>
To: "Hin-Tak Leung" <hintak.leung@gmail.com>,
	ndiswrapper-general@lists.sourceforge.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2
Date: Tue, 29 Sep 2009 11:45:35 +0200	[thread overview]
Message-ID: <200909291145.35972.malte.gell@gmx.de> (raw)
In-Reply-To: <3ace41890909290206g3019a9cbv29048837804f830@mail.gmail.com>


"Hin-Tak Leung" <hintak.leung@gmail.com> wrote

> > So, no need to modify compat-2.6.28.c? Does it automatically happen?
> 
> You may or may not  see any errors at the linker stage (the LD part in
> stage 2). If you get to that point without further error, then, well,
> count yourself lucky and just give "make install ; make unload;
> modprobe -v ar9170" a go.

Ho ho ;-) I got a lot of warnings like this:

 include/linux/tracepoint.h:86:1: warning: this is the location of the 
previous definition

But, it DID compile! Thanx a lot.

To be sure I did a find . -name "*.ko" and got these modules:

./drivers/net/wireless/ath/ath.ko
./net/rfkill/rfkill_backport.ko
./net/wireless/cfg80211.ko
./net/mac80211/mac80211.ko

I just wonder, where is ar9170usb !? I did ./scripts/driver-select ar9170

Malte

  reply	other threads:[~2009-09-29  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200909290956.49681.malte.gell@gmx.de>
2009-09-29  8:51 ` compat-wireless tracepoint error Re: [Ndiswrapper-general] Need help to create driver for Netgear WN111v2 Hin-Tak Leung
2009-09-29  8:58   ` Malte Gell
2009-09-29  9:06     ` Hin-Tak Leung
2009-09-29  9:45       ` Malte Gell [this message]
2009-09-29 10:28         ` Hin-Tak Leung
2009-09-29 11:07           ` Malte Gell
2009-09-29 22:17           ` Malte Gell
2009-09-30  0:57             ` Hin-Tak Leung

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=200909291145.35972.malte.gell@gmx.de \
    --to=malte.gell@gmx.de \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ndiswrapper-general@lists.sourceforge.net \
    /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).