LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Nobin Mathew" <nobin.mathew@gmail.com>
To: "Jiri Slaby" <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	"Robert Hancock" <hancockr@shaw.ca>
Subject: Re: sharing interrupt between PCI device
Date: Wed, 5 Nov 2008 14:50:01 +0530	[thread overview]
Message-ID: <8d6898730811050120k10a20e4em744be45e04cfba94@mail.gmail.com> (raw)
In-Reply-To: <49115AFC.2030400@gmail.com>

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@gmail.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...
>

  reply	other threads:[~2008-11-05  9:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h7+lofM1lpbRM5V4/ti5d7RwXuM@ifi.uio.no>
2008-11-05  0:28 ` sharing interrupt between PCI device Robert Hancock
2008-11-05  7:49   ` Nobin Mathew
2008-11-05  8:36     ` Jiri Slaby
2008-11-05  9:20       ` Nobin Mathew [this message]
2008-11-06  6:11         ` Nobin Mathew
2008-11-06  7:44           ` Nobin Mathew
2008-11-06 21:24             ` Jiri Slaby
2008-11-07  5:46               ` Nobin Mathew
2008-11-08  7:57         ` Grant Grundler
2008-11-08  9:49           ` Jiri Slaby
2008-11-08 11:53             ` Nobin Mathew
2008-11-08 11:57               ` Jiri Slaby
2008-11-08 17:27     ` Grant Grundler
2008-11-08 19:10       ` Jiri Slaby
2008-11-08 19:15         ` Grant Grundler
2008-11-10  6:35           ` Nobin Mathew
2008-11-10  6:39             ` Nobin Mathew
2008-11-10  6:47               ` Nobin Mathew
2008-11-10  7:51             ` Grant Grundler
2008-11-10  7:58               ` Ingo Molnar
2008-11-10 10:31                 ` Nobin Mathew
2008-11-10 15:42                   ` Nobin Mathew
2008-11-10 20:34                     ` Grant Grundler
2008-11-11  4:57                       ` Nobin Mathew
2008-11-11 16:24                         ` Altobelli, David
2008-11-11 18:49                           ` Robert Hancock
2008-11-10 20:33                 ` Grant Grundler
2008-11-03 13:32 Nobin Mathew
2008-11-03 14:44 ` Jiri Slaby

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=8d6898730811050120k10a20e4em744be45e04cfba94@mail.gmail.com \
    --to=nobin.mathew@gmail.com \
    --cc=hancockr@shaw.ca \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@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).