Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org, mcgrof@gmail.com,
	Roy Marples <uberlord@gentoo.org>
Subject: Re: [PATCH] [PATCH] prism54: set carrier flags correctly
Date: Mon, 31 Mar 2008 14:59:50 -0400	[thread overview]
Message-ID: <1206989990.12973.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1206988135-12309-1-git-send-email-linville@tuxdriver.com>

On Mon, 2008-03-31 at 14:28 -0400, John W. Linville wrote:
> From: Roy Marples <uberlord@gentoo.org>
> 
> prism54 should set the carrier flags correctly when it thinks the
> link can be used.
> 
> Signed-off-by: Roy Marples <uberlord@gentoo.org>
> ---
> I found this in my pile from a long time back.  Anyone have any
> comments on it?

Other than the fact that the carrier flag on wireless devices is kind of
useless, it's fine.  I guess it would be somewhat useful if we could
ensure that the carrier would be on _only_ when the card was
successfully associated and authenticated to the requested AP, but until
every driver was converted properly it would be useless because you
couldn't depend on it.

Dan

>  drivers/net/wireless/prism54/isl_ioctl.c  |    5 ++++-
>  drivers/net/wireless/prism54/islpci_dev.c |    4 +++-
>  2 files changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/wireless/prism54/isl_ioctl.c b/drivers/net/wireless/prism54/isl_ioctl.c
> index 838d510..25d42ac 100644
> --- a/drivers/net/wireless/prism54/isl_ioctl.c
> +++ b/drivers/net/wireless/prism54/isl_ioctl.c
> @@ -2093,8 +2093,11 @@ link_changed(struct net_device *ndev, u32 bitrate)
>  		} else
>  			send_simple_event(netdev_priv(ndev),
>  					  "Link established");
> -	} else
> +		netif_carrier_on(ndev);
> +	} else {
>  		send_simple_event(netdev_priv(ndev), "Link lost");
> +		netif_carrier_off(ndev);
> +	}
>  }
>  
>  /* Beacon/ProbeResp payload header */
> diff --git a/drivers/net/wireless/prism54/islpci_dev.c b/drivers/net/wireless/prism54/islpci_dev.c
> index f057fd9..9c8c6f2 100644
> --- a/drivers/net/wireless/prism54/islpci_dev.c
> +++ b/drivers/net/wireless/prism54/islpci_dev.c
> @@ -386,7 +386,9 @@ islpci_open(struct net_device *ndev)
>  	}
>  
>  	netif_start_queue(ndev);
> -/*      netif_mark_up( ndev ); */
> +
> +	/* Turn off carrier unless we know we have associated */
> +	netif_carrier_off(ndev);
>  
>  	return 0;
>  }


  reply	other threads:[~2008-03-31 19:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-31 18:28 [PATCH] [PATCH] prism54: set carrier flags correctly John W. Linville
2008-03-31 18:59 ` Dan Williams [this message]
2008-04-01 19:17   ` Luis R. Rodriguez
2008-04-01 20:43     ` Dan Williams

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=1206989990.12973.9.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=uberlord@gentoo.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