linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George <george.news@gmx.net>
To: Kalle Valo <kvalo@adurom.com>
Cc: Grazvydas Ignotas <notasas@gmail.com>,
	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: Mon, 25 Oct 2010 10:33:53 +0200	[thread overview]
Message-ID: <4CC540F1.2070303@gmx.net> (raw)
In-Reply-To: <87ocaj1120.fsf@purkki.adurom.net>

On 25/10/2010 4:03, Kalle Valo wrote:
> George<george.news@gmx.net>  writes:
>
>> 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?
>
> If you get nothing but zeros back from the device, most likely that
> means that it's not powered up properly.
>
> wl1251 chip on n900 is powered up by using a gpio line. I'm worried
> that the struct wl12xx_platform_data wl1251 wireless-compat driver
> expects (defined in /include/linux/wl12xx.h) doesn't match what the
> old maemo kernel provides. Unfortunately I can't remember anymore what
> the platform data was like in maemo kernels and there's no easy way
> for me to check that right now.
>

Thanks a lot for that hint. Now I'm involved in another issue but when I 
have more time I will look at those .h, but don't expect too much from 
me as I'm not expert but just user.

Thanks a lot.

  reply	other threads:[~2010-10-25  7:49 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
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 [this message]
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=4CC540F1.2070303@gmx.net \
    --to=george.news@gmx.net \
    --cc=GNUtoo@no-log.org \
    --cc=kvalo@adurom.com \
    --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).