Linux wireless drivers development
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Mark Wallis <mwallis@serialmonkey.com>
Cc: wireless@lists.tuxdriver.org, rt2400-devel@lists.sourceforge.net
Subject: Re: Getting dscape running
Date: Tue, 30 Jan 2007 18:48:54 -0500	[thread overview]
Message-ID: <9e4733910701301548q2bda029fs9dd1bde06b8cadea@mail.gmail.com> (raw)
In-Reply-To: <03f001c744c2$9ac897d0$d059c770$@com>

On 1/30/07, Mark Wallis <mwallis@serialmonkey.com> wrote:
> > check out my other post
>
> It would be helpful if you could provide a debug trace as well.
>
> > This is part of what makes working on wireless hard, the pieces are
> > scattered everywhere.
>
> Probably best to move this discussion to rt2400-devel and let us check
> if the problem still exists in our latest CVS. From there, if assoc
> is working fine you can bounce over to the NetworkManager list and go
> from there.

ralink CVS won't build with the current wireless-dev tree.
It tool a little while to check since I had to rebuild my kernel and
turn debugfs on.
I'll try Pavel's suggestions next.

jonsmirl@jonsmirl:/extra/ralink/rt2x00$ make
  CC [M]  /extra/ralink/rt2x00/ieee80211/ieee80211.o
In file included from /extra/ralink/rt2x00/ieee80211/ieee80211.c:13:
include/linux/netdevice.h:406: error: duplicate member 'ax25_ptr'
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function 'ieee80211_tx_h_rts':
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error:
'IEEE80211_HW_SOFTWARE_RTS' undeclared (first use in this function)
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error: (Each
undeclared identifier is reported only once
/extra/ralink/rt2x00/ieee80211/ieee80211.c:858: error: for each
function it appears in.)
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function
'ieee80211_tx_h_sequence':
/extra/ralink/rt2x00/ieee80211/ieee80211.c:947: error:
'IEEE80211_HW_SOFTWARE_SEQUENCE' undeclared (first use in this
function)
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function 'ieee80211_beacon_get':
/extra/ralink/rt2x00/ieee80211/ieee80211.c:1857: error:
'IEEE80211_HW_SOFTWARE_SEQUENCE' undeclared (first use in this
function)
/extra/ralink/rt2x00/ieee80211/ieee80211.c: In function '__ieee80211_if_config':
/extra/ralink/rt2x00/ieee80211/ieee80211.c:1993: error: 'struct
ieee80211_if_conf' has no member named 'beacon_control'
make[2]: *** [/extra/ralink/rt2x00/ieee80211/ieee80211.o] Error 1
make[1]: *** [_module_/extra/ralink/rt2x00] Error 2
make: *** [default] Error 2
jonsmirl@jonsmirl:/extra/ralink/rt2x00$



>
> Regards,
> Mark Wallis
> rt2x00 Project Admin
> mwallis@serialmonkey.com
>
>
>
>
>
>


-- 
Jon Smirl
jonsmirl@gmail.com
_______________________________________________
wireless mailing list
wireless@lists.tuxdriver.org
http://lists.tuxdriver.org/mailman/listinfo/wireless

  reply	other threads:[~2007-01-30 23:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 22:15 Getting dscape running Jon Smirl
2007-01-30 22:24 ` Mark Wallis
2007-01-30 22:41   ` Jon Smirl
2007-01-30 23:01     ` Mark Wallis
2007-01-30 23:48       ` Jon Smirl [this message]
2007-01-30 22:24 ` Pavel Roskin
2007-01-30 22:36   ` Jon Smirl
2007-01-30 22:54     ` Pavel Roskin
2007-01-31  0:09       ` Jon Smirl
2007-01-31  0:16       ` Michael Wu
2007-01-31  0:19       ` Jon Smirl

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=9e4733910701301548q2bda029fs9dd1bde06b8cadea@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=mwallis@serialmonkey.com \
    --cc=rt2400-devel@lists.sourceforge.net \
    --cc=wireless@lists.tuxdriver.org \
    /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