From: "Franky Lin" <frankyl@broadcom.com>
To: "Denis 'GNUtoo' Carikli" <GNUtoo@no-log.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: brcmfmac + compat wireless + 2.6.35
Date: Sat, 10 Dec 2011 12:46:13 -0800 [thread overview]
Message-ID: <4EE3C515.5050307@broadcom.com> (raw)
In-Reply-To: <1323539463-6072-1-git-send-email-GNUtoo@no-log.org>
Hi Denis,
On 12/10/2011 09:51 AM, Denis 'GNUtoo' Carikli wrote:
>> I will submit a patch too add the dummy handler.
> Since the patch hasn't shown up yet, I decided to give a try,
> But I failed:
I saw the patch you sent. I have one queued up internally but am happy
to take yours. Does the patch work or not?
> The patch which will follow blocks the phone(ssh doens't respond
> anymore), I really wonder what's wrong with it since it does
> something very similar to the bcm4329 driver.
> The last printk are theses ones:
> [ 63.436157] wifi_set_power = 1
> [ 63.641585] wifi_set_carddetect = 1
> [ 63.646195] sdhci_s3c_force_presence_change : Enter
> [ 63.780660] mmc2: queuing unknown CIS tuple 0x80 (50 bytes)
> [ 63.796865] mmc2: queuing unknown CIS tuple 0x80 (7 bytes)
> [ 63.843426] mmc2: queuing unknown CIS tuple 0x80 (3 bytes)
> [ 63.851883] mmc2: new SDIO card at address 0001
Did you try to enable more debug trace? Looks like sdio probe has never
been called.
Franky
next prev parent reply other threads:[~2011-12-10 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 15:00 brcmfmac + compat wireless + 2.6.35 Denis 'GNUtoo' Carikli
2011-11-22 19:46 ` Denis 'GNUtoo' Carikli
2011-11-22 22:16 ` Franky Lin
2011-11-23 15:59 ` Denis 'GNUtoo' Carikli
2011-12-10 17:51 ` Denis 'GNUtoo' Carikli
2011-12-10 17:51 ` [PATCH] brcm80211: fmac: try to add a dummy interupt handler for sdio function 2 Denis 'GNUtoo' Carikli
2011-12-10 20:46 ` Franky Lin [this message]
2011-12-10 22:57 ` brcmfmac + compat wireless + 2.6.35 Denis 'GNUtoo' Carikli
2011-12-18 11:33 ` Denis 'GNUtoo' Carikli
2011-12-19 18:29 ` Franky Lin
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=4EE3C515.5050307@broadcom.com \
--to=frankyl@broadcom.com \
--cc=GNUtoo@no-log.org \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).