linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Clayton <chris2553@googlemail.com>
To: Chris Vine <chris@cvine.freeserve.co.uk>
Cc: Ivo van Doorn <ivdoorn@gmail.com>, Dan Williams <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	rt2400-devel@lists.sourceforge.net
Subject: Re: [Rt2400-devel] 2.6.25-rc2 regression in rt61pci wireless driver
Date: Fri, 22 Feb 2008 07:39:15 +0000	[thread overview]
Message-ID: <200802220739.15366.chris2553@googlemail.com> (raw)
In-Reply-To: <1203636027.3186.5.camel@boulder.homenet>

On Thursday 21 February 2008, Chris Vine wrote:
> On Thu, 2008-02-21 at 23:04 +0000, Chris Clayton wrote:
> > On Thursday 21 February 2008, Ivo van Doorn wrote:
> > > On Thursday 21 February 2008, Chris Vine wrote:
> [snip]
> > > > This probably explains the problem another user reported with rt61.
> > > 
> > > Perhaps something similar like:
> > > http://bugzilla.kernel.org/show_bug.cgi?id=10058
> > > in there a reference is made to the following patch:
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25-rc2/2.6.25-rc2-mm1/broken-out/revert-send-a-single-notification-on-device-state-changes.patch
> > > 
> > > Does applying that help?
> > 
> > I'm afraid not, Ivo. The test I ran last night was against 2.6.25.-rc2-git4 and
> > that already has this patch applied. Furthermore, I have another card that uses
> > the rtl8180 driver and that works reliably. I, therefore, suspect that my problem
> > lies within the rt61pci driver or the rt2x00 infrastructure.
> 
> Does the same happen with 2.0.14 under kernel 2.6.24?

Unfortunately, a 2.6.24.2 tree with the drivers/net/wireless/rt2x00 directory replaced with that from 2.6.25-rc2-git4 doesn't build:

In file included from drivers/net/wireless/rt2x00/rt2x00dev.c:29:
drivers/net/wireless/rt2x00/rt2x00.h:942: warning: `struct ieee80211_bss_conf' declared inside parameter list
drivers/net/wireless/rt2x00/rt2x00.h:942: warning: its scope is only this definition or declaration, which is probably not what you want

[...]

drivers/net/wireless/rt2x00/rt2x00dev.c: In function `rt2x00lib_configuration_scheduled':
drivers/net/wireless/rt2x00/rt2x00dev.c:484: error: storage size of `bss_conf' isn't known
drivers/net/wireless/rt2x00/rt2x00dev.c:494: error: `BSS_CHANGED_ERP_PREAMBLE' undeclared (first use in this function)
drivers/net/wireless/rt2x00/rt2x00dev.c:494: error: (Each undeclared identifier is reported only once
drivers/net/wireless/rt2x00/rt2x00dev.c:494: error: for each function it appears in.)
drivers/net/wireless/rt2x00/rt2x00dev.c:484: warning: unused variable `bss_conf'
drivers/net/wireless/rt2x00/rt2x00dev.c: In function `rt2x00lib_beacondone_scheduled':
drivers/net/wireless/rt2x00/rt2x00dev.c:511: warning: passing arg 2 of `ieee80211_beacon_get' makes integer from pointer without a cast

> 
> Chris
> 
> 
> 
> 

-- 
Beauty is in the eye of the beerholder.

  reply	other threads:[~2008-02-22  7:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-16 12:06 2.6.25-rc2 regression in rt61pci wireless driver Chris Clayton
2008-02-18 18:11 ` Ivo van Doorn
2008-02-18 18:16   ` Ivo van Doorn
2008-02-18 22:51   ` Chris Clayton
2008-02-19  9:26     ` Ivo van Doorn
2008-02-19 19:00       ` Chris Clayton
2008-02-19 19:46         ` Ivo van Doorn
2008-02-19 20:44           ` Chris Clayton
2008-02-19 21:03             ` Ivo van Doorn
2008-02-19 23:04           ` [Rt2400-devel] " Chris Vine
2008-02-20 16:05             ` Dan Williams
2008-02-20 20:27               ` Chris Vine
2008-02-20 20:50                 ` Ivo van Doorn
2008-02-20 21:16                   ` Chris Vine
2008-02-21 21:07                     ` Chris Vine
2008-02-21 21:51                       ` Ivo van Doorn
2008-02-21 22:46                         ` Chris Vine
2008-02-21 22:51                           ` Ivo van Doorn
2008-02-21 23:04                         ` Chris Clayton
2008-02-21 23:20                           ` Chris Vine
2008-02-22  7:39                             ` Chris Clayton [this message]
2008-02-22 19:11                               ` Ivo van Doorn
2008-02-22 20:33                               ` Chris Vine
2008-02-20 22:13                   ` Chris Clayton
2008-02-22 15:46   ` Chris Clayton
2008-02-22 19:47     ` Ivo van Doorn
2008-02-25 21:04       ` Chris Clayton
2008-02-25 22:09         ` Ivo Van Doorn
2008-02-26 19:11           ` Chris Clayton
2008-02-26 19:48             ` John W. Linville
2008-02-26 20:30               ` Ivo Van Doorn
2008-02-26 21:44                 ` Stefano Brivio
2008-02-26 21:13               ` Chris Clayton
2008-02-26 21:38                 ` Stefano Brivio
2008-02-26 22:36                   ` Chris Clayton
2008-02-27  7:26                     ` Stefano Brivio
2008-02-27 15:51                       ` John W. Linville
2008-02-27 17:25                         ` John W. Linville
2008-02-27 17:45                           ` Chris Clayton
2008-03-02 10:33                           ` Stefano Brivio
2008-03-02 15:11                             ` Chris Clayton

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=200802220739.15366.chris2553@googlemail.com \
    --to=chris2553@googlemail.com \
    --cc=chris@cvine.freeserve.co.uk \
    --cc=dcbw@redhat.com \
    --cc=ivdoorn@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rt2400-devel@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).