diff for duplicates of <20040516152113.GA9390@convergence.de> diff --git a/a/1.txt b/N1/1.txt index 1345039..c69134e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -19,52 +19,3 @@ I would appreciate it if someone could look it over (full source is in linux/drivers/media/common/saa7146_core.c). The driver is known to work on a variety of platforms, including one TX49 based development system (last tested a few months back, though). - - -From your first posting: - - PCI: Setting latency timer of device 0000:00:0a.0 to 64 - irq 23: nobody cared! - Call Trace: [snipped] - handlers: - [<c004b570>] - Disabling IRQ #23 - saa7146: found saa7146 @ mem b2080800 (revision 1, irq 23) (0x13c2,0x1011). - -Second try with debug enabled: - - saa7146: saa7146_register_extension(): ext:c001efb0 - saa7146: register extension 'budget_ci dvb'. - saa7146: saa7146_init_one(): pci:83fdac00 - irq 23: nobody cared! - - -saa7146_init_one() does the following: - /* disable all irqs */ - saa7146_write(dev, IER, 0); - ... - if (request_irq(dev->pci->irq, interrupt_hw, SA_SHIRQ | SA_INTERRUPT, - dev->name, dev)) - {error...} - ... - INFO(("found saa7146 @ mem %p (revision %d, irq %d) (0x%04x,0x%04x).\n", ...)); - -interrupt_hw() does: - /* read out the interrupt status register */ - isr = saa7146_read(dev, ISR); - - /* is this our interrupt? */ - if ( 0 == isr ) { - /* nope, some other device */ - return IRQ_NONE; - } - ... - return IRQ_HANDLED; - - -In essence, I believe something other than the saa7146 must be asserting irq 23. -Or is it possible that a bug in the PCI init stuff in saa7146_core.c can -cause this? Any hints how we could debug this would be welcome. - - -Johannes diff --git a/a/content_digest b/N1/content_digest index 52de251..06805f7 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -28,55 +28,6 @@ "I would appreciate it if someone could look it over (full source\n" "is in linux/drivers/media/common/saa7146_core.c). The driver is\n" "known to work on a variety of platforms, including one TX49 based\n" - "development system (last tested a few months back, though).\n" - "\n" - "\n" - "From your first posting:\n" - "\n" - " PCI: Setting latency timer of device 0000:00:0a.0 to 64\n" - " irq 23: nobody cared!\n" - " Call Trace: [snipped]\n" - " handlers:\n" - " [<c004b570>]\n" - " Disabling IRQ #23\n" - " saa7146: found saa7146 @ mem b2080800 (revision 1, irq 23) (0x13c2,0x1011).\n" - "\n" - "Second try with debug enabled:\n" - "\n" - " saa7146: saa7146_register_extension(): ext:c001efb0\n" - " saa7146: register extension 'budget_ci dvb'.\n" - " saa7146: saa7146_init_one(): pci:83fdac00\n" - " irq 23: nobody cared!\n" - "\n" - "\n" - "saa7146_init_one() does the following:\n" - " /* disable all irqs */\n" - "\tsaa7146_write(dev, IER, 0);\n" - "\t...\n" - " if (request_irq(dev->pci->irq, interrupt_hw, SA_SHIRQ | SA_INTERRUPT,\n" - " dev->name, dev))\n" - " {error...}\n" - " ...\n" - " INFO((\"found saa7146 @ mem %p (revision %d, irq %d) (0x%04x,0x%04x).\\n\", ...));\n" - "\n" - "interrupt_hw() does:\n" - " /* read out the interrupt status register */\n" - " isr = saa7146_read(dev, ISR);\n" - "\n" - " /* is this our interrupt? */\n" - " if ( 0 == isr ) {\n" - " /* nope, some other device */\n" - " return IRQ_NONE;\n" - " }\n" - " ...\n" - " return IRQ_HANDLED;\n" - "\n" - "\n" - "In essence, I believe something other than the saa7146 must be asserting irq 23.\n" - "Or is it possible that a bug in the PCI init stuff in saa7146_core.c can\n" - "cause this? Any hints how we could debug this would be welcome.\n" - "\n" - "\n" - Johannes + development system (last tested a few months back, though). -d84efd84d3e6c08517ed937220ed69d694918e1c00f1baca3fed7185dee8c4fb +478ce3bb5b52603906d253961028838baa8351b31c1ac13d7361d67d58d4d3f5
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox