public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Felix Radensky <felix@embedded-sol•com>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: Mahajan Vivek-B08308 <B08308@freescale•com>,
	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 22:28:30 +0200	[thread overview]
Message-ID: <4B2A946E.4040907@embedded-sol.com> (raw)
In-Reply-To: <EBE3ECA5-AC1B-4E1C-A0DA-89260D0F03F6@kernel.crashing.org>

Hi, Kumar
Kumar Gala wrote:
> On Dec 17, 2009, at 2:59 AM, Mahajan Vivek-B08308 wrote:
>
>   
>>> 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 ?
>>>       
>> Correct
>>     
>
> I'm confused.  What's the issue with IRQ0 on the P2020RDB?  Is it used for another purpose?
>   

There's a problem with IRQ0 with respect to mini-PCI-E slot. I have 
Atheros wireless card plugged
into it. ath9k wireless driver for this card uses legacy PCI-E 
interrupts, and I get "irq 16: nobody cared"
message when driver executes request_irq(). Vivek has come to a 
conclusion that the problem is
related to incorrect IRQ0 routing for mini-PCI-E slot on P2020RDB.

Felix.

  reply	other threads:[~2009-12-17 20:28 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
2009-12-17  8:59                 ` Mahajan Vivek-B08308
2009-12-17 17:01                   ` Kumar Gala
2009-12-17 20:28                     ` Felix Radensky [this message]
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=4B2A946E.4040907@embedded-sol.com \
    --to=felix@embedded-sol$(echo .)com \
    --cc=B08308@freescale$(echo .)com \
    --cc=B10812@freescale$(echo .)com \
    --cc=galak@kernel$(echo .)crashing.org \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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