linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George <george.news@gmx.net>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Luciano Coelho <luciano.coelho@nokia.com>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>,
	Bob Copeland <me@bobcopeland.com>,
	Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Compat-wireless N900
Date: Wed, 20 Oct 2010 09:37:51 +0200	[thread overview]
Message-ID: <4CBE9C4F.7050806@gmx.net> (raw)
In-Reply-To: <AANLkTik3ZdZov4OTn0NnnPe_ZUaRh_w0db4bwLYVGCRR@mail.gmail.com>

On 19/10/2010 17:18, Grazvydas Ignotas wrote:
>> I have also set the debug ALL mode to see if I get something that can help
>> you out on finding the problem.
>>
>> When uploading only wl1251 nothing appears in dmesg. But when uploading
>> module spi, I got the following info: http://pastebin.com/ysdTSDnB
>
> You need both wl1251 and spi. This is normal output, you should get
> wlan0 interface at this point.
> --

Yes, that is what I was expecting from the begining but although phy0 
should appear in /sys/class/ieee80211, this directory is empty :(

It seems that it tries to do something but it is not finally done. 
However, as you can see it seems there is no error (at least reported). 
Could it be that spi_read buf is almost everytime reading 00 00 00 00?

Another issue is that I have to manually upload the spi module as by 
default it only uploads wl1251 but not the spi. But this is not a big deal.

Again, thank you all for the help... You are almost there (I cannot say 
we as I've been only following your advices).

TA

  reply	other threads:[~2010-10-20  6:53 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
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 [this message]
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=4CBE9C4F.7050806@gmx.net \
    --to=george.news@gmx.net \
    --cc=GNUtoo@no-log.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luciano.coelho@nokia.com \
    --cc=mcgrof@gmail.com \
    --cc=me@bobcopeland.com \
    --cc=notasas@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).