From: Felix Radensky <felix@embedded-sol.com>
To: Mahajan Vivek-B08308 <B08308@freescale.com>
Cc: linuxppc-dev@ozlabs.org, Aggrwal Poonam-B10812 <B10812@freescale.com>
Subject: Re: Problem with mini-PCI-E slot on P2020RDB
Date: Thu, 17 Dec 2009 10:56:26 +0200 [thread overview]
Message-ID: <4B29F23A.9070001@embedded-sol.com> (raw)
In-Reply-To: <0949C49693EF1A47A54B0F0113CDB4A60767E8@zin33exm23.fsl.freescale.net>
Mahajan Vivek-B08308 wrote:
>> From:
>> linuxppc-dev-bounces+vivek.mahajan=freescale.com@lists.ozlabs.
>> org
>> [mailto:linuxppc-dev-bounces+vivek.mahajan=freescale.com@lists
>> .ozlabs.org] On Behalf Of Felix Radensky
>> Sent: Thursday, December 17, 2009 12:52 PM
>>
>>> I just noticed a MSI enable bit in
>>> drivers/net/wireless/ath/ath9k/reg.h
>>> as under, may be we need to trun this on:-
>>>
>>> reg.h:1013:#define AR_PCIE_MSI 0x4094
>>> reg.h:1014:#define AR_PCIE_MSI_ENABLE
>>>
>> 0x00000001
>>
>>>
>>>
>> According to ath9k developers adding MSI support to the
>> driver is not trivial.
>> They've tried once, it didn't work and they gave up. Any
>> chance I can use mini-PCI-E slot without MSI ?
>>
>
> So, even after enabling the above bit, there were no MSI
> interrupts from this card. If we look at some of the GbE
> or SATA drivers, adding MSI is not that hard. ath9k can
> be an exception.
>
Yes, I've enabled that bit, but didn't get any interrupt.
> I reported this issue to the p2020 board designer; but
> unfortunately he is out until 1/4/10. It could be a missing
> pull-up issue at IRQ0 or some thing else, I don't know.
>
>
Thanks a lot. If I understand you correctly, the only way I can
get ath9k driver to work on this board using legacy interrupts is
to wait for a hardware fix. Right ?
Felix.
next prev parent reply other threads:[~2009-12-17 8:56 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 21:25 Problem with mini-PCI-E slot on P2020RDB Felix Radensky
2009-12-16 6:49 ` Mahajan Vivek-B08308
2009-12-16 9:26 ` Felix Radensky
2009-12-16 9:52 ` Mahajan Vivek-B08308
2009-12-16 12:00 ` Felix Radensky
2009-12-16 12:27 ` Mahajan Vivek-B08308
2009-12-17 7:22 ` Felix Radensky
2009-12-17 7:59 ` Mahajan Vivek-B08308
2009-12-17 8:56 ` Felix Radensky [this message]
2009-12-17 8:59 ` Mahajan Vivek-B08308
2009-12-17 17:01 ` Kumar Gala
2009-12-17 20:28 ` Felix Radensky
2011-04-07 17:20 ` Leon Woestenberg
2011-04-08 3:53 ` Kushwaha Prabhakar-B32579
2011-04-11 8:23 ` Fabian Bertholm
2011-04-11 9:06 ` Kushwaha Prabhakar-B32579
2011-04-11 8:39 ` Felix Radensky
2011-04-11 11:09 ` Kushwaha Prabhakar-B32579
2011-04-11 13:45 ` Felix Radensky
[not found] <071A08F2C6A57E4E94D980ECA553F87417069A@039-SN1MPN1-004.039d.mgd.msft.net>
2011-04-12 4:05 ` Aggrwal Poonam-B10812
2011-04-12 4:35 ` Benjamin Herrenschmidt
2011-04-12 4:45 ` Felix Radensky
2011-04-12 4:54 ` Felix Radensky
2011-04-13 9:22 ` Leon Woestenberg
[not found] <470DB7CE2CD0944E9436E7ADEFC02FE314BF85@039-SN1MPN1-001.039d.mgd.msft.net>
2011-04-13 4:40 ` Kushwaha Prabhakar-B32579
[not found] <45903308677306428B6EE7E6FF5A520410D3E6@039-SN1MPN1-004.039d.mgd.msft.net>
2011-04-15 6:27 ` Kushwaha Prabhakar-B32579
2011-04-15 7:20 ` Felix Radensky
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=4B29F23A.9070001@embedded-sol.com \
--to=felix@embedded-sol.com \
--cc=B08308@freescale.com \
--cc=B10812@freescale.com \
--cc=linuxppc-dev@ozlabs.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).