linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elvis Dowson <elvis.dowson@mac.com>
To: Ohad Ben-Cohen <ohad@wizery.com>
Cc: Linux Wireless Mailing List <linux-wireless@vger.kernel.org>,
	panduranga <x0125717@ti.com>, Pedro Jara <pedrojara@ti.com>
Subject: Problem bringing up wlan0 interface up with mainline wl1271 drivers
Date: Fri, 17 Dec 2010 04:23:32 +0400	[thread overview]
Message-ID: <C77CCCD3-2467-4363-A513-05B68B9F57F6@mac.com> (raw)
In-Reply-To: <AANLkTikESPwcaxUSDd3B=Oh7kBD-QpndKRHmu9-roDqs@mail.gmail.com>

Hi,

On Dec 12, 2010, at 1:24 AM, Ohad Ben-Cohen wrote:

>> When I build the TI WiLink drivers from the ti rowboat hardware/ti/wlan project
> 
> The linux-omap community can help you with mainline drivers, but no so
> much with proprietary ones. Why don't you use the upstream wl12xx
> driver ?

I've built linux kernel 2.6.37-rc6, and patched board-omap3beagle.c to interface with MMC2 SDIO controller, 
but I'm unable to bring the wlan0 interface up.

Here are the messages during kernel boot:

[    0.000000] wlan_mux_init: Configuring mux settings for wl1271 wlan module
[    0.077117] regulator: vwl1271: 1850 mV normal standby
[    2.171813] mmc1: mmc_rescan: trying to init card at 400000 Hz
[    2.323120] mmc1: card claims to support voltages below the defined range. These will be ignored.
[    2.368865] mmc1: queuing unknown CIS tuple 0x91 (3 bytes)
[    2.392150] mmc1: new SDIO card at address 0001
[    2.787597] wl1271: loaded
[    2.790802] wl1271: initialized

# ifconfig -a
lo        Link encap:Local Loopback  
          LOOPBACK  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

# ifconfig wlan0 up
SIOCSIFFLAGS: Cannot assign requested address

What could the reason be?

Elvis Dowson

       reply	other threads:[~2010-12-17  0:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57CB308D-7237-46D7-9AF8-7093F52682E8@mac.com>
     [not found] ` <AANLkTikESPwcaxUSDd3B=Oh7kBD-QpndKRHmu9-roDqs@mail.gmail.com>
2010-12-17  0:23   ` Elvis Dowson [this message]
2010-12-17  5:11     ` Problem bringing up wlan0 interface up with mainline wl1271 drivers panduranga
2010-12-17  8:36       ` Elvis Dowson
     [not found]         ` <AANLkTinejL9LeocQPzjrqrCFYbrF9wqpD9dSyfEVu8us@mail.gmail.com>
2010-12-17  8:59           ` Arik Nemtsov
2010-12-17  9:44           ` Elvis Dowson
2010-12-17 10:12             ` Arik Nemtsov
2010-12-17 10:25               ` Elvis Dowson
2010-12-17 10:34                 ` Arik Nemtsov
2010-12-17 10:37                   ` Elvis Dowson
2010-12-17 11:12                     ` Elvis Dowson
2010-12-17 10:38                 ` Luciano Coelho
2011-08-10 11:34                   ` amit.gemini
2010-12-17  9:33       ` Elvis Dowson

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=C77CCCD3-2467-4363-A513-05B68B9F57F6@mac.com \
    --to=elvis.dowson@mac.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=pedrojara@ti.com \
    --cc=x0125717@ti.com \
    /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).