All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: linville@tuxdriver.com
Cc: bcm43xx-dev@lists.berlios.de, netdev@vger.kernel.org,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: Associate on 'ifconfig up'
Date: Sun, 7 May 2006 15:06:06 +0200	[thread overview]
Message-ID: <200605071506.06552.mb@bu3sch.de> (raw)
In-Reply-To: <1146939849.2503.108.camel@shinybook.infradead.org>

On Saturday 06 May 2006 20:24, David Woodhouse wrote:
> On Fri, 2006-05-05 at 17:38 +0100, David Woodhouse wrote:
> > I still need this hack to work around the fact that softmac doesn't
> > attempt to associate when we bring the device up...
> 
> It'd be quite good to get this fixed in 2.6.17 too. Otherwise, the
> device doesn't manage to associate if you use the fairly common sequence
> of iwconfig then dhclient.
> 
> It's a bit of an evil hack and it should really be fixed in softmac --
> but it's only moving an _existing_ hack from one place in the driver to
> another.
> 
> Signed-off-by: David Woodhouse <dwmw2@infradead.org>

Signed-off-by: Michael Buesch <mb@bu3sch.de>

John, please try to push this before 2.6.17.
Thanks.

> --- linux-2.6.16.ppc/drivers/net/wireless/bcm43xx/bcm43xx_main.c.orig	2006-05-05 17:14:26.000000000 +0100
> +++ linux-2.6.16.ppc/drivers/net/wireless/bcm43xx/bcm43xx_main.c	2006-05-05 17:15:19.000000000 +0100
> @@ -3263,6 +3263,9 @@ static int bcm43xx_init_board(struct bcm
>  	bcm43xx_sysfs_register(bcm);
>  	//FIXME: check for bcm43xx_sysfs_register failure. This function is a bit messy regarding unwinding, though...
>  
> +	/*FIXME: This should be handled by softmac instead. */
> +	schedule_work(&bcm->softmac->associnfo.work);
> +
>  	assert(err == 0);
>  out:
>  	return err;
> @@ -3937,9 +3940,6 @@ static int bcm43xx_resume(struct pci_dev
>  
>  	netif_device_attach(net_dev);
>  	
> -	/*FIXME: This should be handled by softmac instead. */
> -	schedule_work(&bcm->softmac->associnfo.work);
> -
>  	dprintk(KERN_INFO PFX "Device resumed.\n");
>  
>  	return 0;
> 

-- 
Greetings Michael.

  reply	other threads:[~2006-05-07 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1146847107.2766.13.camel@pmac.infradead.org>
2006-05-06 18:24 ` Associate on 'ifconfig up' David Woodhouse
2006-05-07 13:06   ` Michael Buesch [this message]
2006-05-09 18:53     ` David Woodhouse

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=200605071506.06552.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=bcm43xx-dev@lists.berlios.de \
    --cc=dwmw2@infradead.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.