[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d6898730811052211k695d208r53609701af633c2d@mail.gmail.com>
Date: Thu, 6 Nov 2008 11:41:00 +0530
From: "Nobin Mathew" <nobin.mathew@...il.com>
To: linux-kernel@...r.kernel.org
Cc: linux-pci@...r.kernel.org, "Robert Hancock" <hancockr@...w.ca>,
"Jiri Slaby" <jirislaby@...il.com>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>
Subject: Re: sharing interrupt between PCI device
Hi
Can somebody tell me what is going wrong in the driver. If you need
any further information please tell me
Thanks
Nobin Mathew
On Wed, Nov 5, 2008 at 2:50 PM, Nobin Mathew <nobin.mathew@...il.com> wrote:
> Hi
>
>
> Code is here
> first one USB Virual input devices
>
> http://lxr.linux.no/linux+v2.6.27.4/drivers/usb/core/hcd-pci.c
>
> Second one is hp-ilo driver
>
> http://lxr.linux.no/linux+v2.6.27.4/drivers/misc/hpilo.c
>
>
> Thanks
> Nobin Mathew.
>
>
> On Wed, Nov 5, 2008 at 2:06 PM, Jiri Slaby <jirislaby@...il.com> wrote:
>> On 11/05/2008 08:49 AM, Nobin Mathew wrote:
>>> Hi
>>>
>>> This is the system information X86_64 platform Xeon dual core processor.
>>>
>>> I saw the pci_disable_device () it is calling pcibios_disable_device
>>> () and this is is defined as
>>>
>>> void pcibios_disable_device (struct pci_dev *dev)
>>> {
>>> pcibios_disable_resources(dev);
>>> if (pcibios_disable_irq)
>>> pcibios_disable_irq(dev);
>>> }
>>>
>>> In i386 platform, I could not find a definition for these calls in
>>> x86_64 platform, i think it is using i386 platform code.
>>
>> Well, will you show us the code, so that we needn't to crystal gaze? It's pretty
>> hard to say what happens, if we don't see what you do in the driver...
>>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists