linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George <george.news@gmx.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>,
	linux-wireless@vger.kernel.org
Subject: Re: Compat-wireless N900
Date: Fri, 15 Oct 2010 08:42:15 +0200	[thread overview]
Message-ID: <4CB7F7C7.7030804@gmx.net> (raw)
In-Reply-To: <AANLkTi=1Ar-gzRaskHGDLmkaDnr=9+oZnA=qBLCYcUAi@mail.gmail.com>

On 14/10/2010 20:03, Luis R. Rodriguez wrote:
> On Thu, Oct 14, 2010 at 11:09 AM, George<george.news@gmx.net>  wrote:
>
>> I have tried using even insmod and the modules load perfectly but the wlan
>> device doesn't show up.
>
> Then that likely means you are not loading the right module.
>
>> In dmesg nothing is displayed except for the cfg80211 and when I rmmod the
>> module wl1251 (wl1251: removed or similar)
>>
>> I'm still wondering what the hell I have to do.
>
> Are you sure you have the right module?

Yes. The driver is the wl1251 family. As I said in previous posts and 
from what some guys in the IRC channel tried to guess, it seems that the 
problem might be in that the spi interface is specific for any device, 
and in the n900 might be different from the one implemented in 
compat-wireless.

I'm a bit suprised about this fact, but they know more than I.

TA

>    Luis
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>


  reply	other threads:[~2010-10-15  5:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-14  8:24 Compat-wireless N900 George
2010-10-14 15:57 ` Denis 'GNUtoo' Carikli
2010-10-14 17:17   ` Luis R. Rodriguez
2010-10-14 18:09     ` George
2010-10-14 18:03       ` Luis R. Rodriguez
2010-10-15  6:42         ` George [this message]
2010-10-15 18:01           ` Luis R. Rodriguez
2010-10-17  9:01             ` George
2010-10-18 16:34               ` George
2010-10-18 17:21                 ` Luis R. Rodriguez
2010-10-18 19:04                   ` George
2010-10-18 18:41                     ` Luciano Coelho
2010-10-18 19:02                       ` Luciano Coelho
2010-10-19  8:12                         ` George
2010-10-19 13:52                           ` Grazvydas Ignotas
2010-10-19 15:16                             ` George
2010-10-19 14:38                               ` Grazvydas Ignotas
2010-10-19 15:52                                 ` George
2010-10-19 15:18                                   ` Grazvydas Ignotas
2010-10-20  7:37                                     ` George
2010-10-20  8:44                                       ` Grazvydas Ignotas
2010-10-20 12:24                                         ` George
2010-10-25  2:03                                       ` Kalle Valo
2010-10-25  8:33                                         ` George
2010-10-19 15:18                               ` George
2010-10-14 17:29   ` George

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=4CB7F7C7.7030804@gmx.net \
    --to=george.news@gmx.net \
    --cc=GNUtoo@no-log.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.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).