http://bugzilla.kernel.org/show_bug.cgi?id=6082
------- Additional Comments From [EMAIL PROTECTED] 2006-02-17 02:55 ------- Created an attachment (id=7381) --> (http://bugzilla.kernel.org/attachment.cgi?id=7381&action=view) patch to invoke pci_enable_device() when using old PCI detect If pci=routeirq helps, this means that the driver did not call pci_enable_device(), and is therefore using a bogus IRQ number (recent kernels perform IRQ routing in pci_enable_device(), and pdev->irq does not have the correct value until that function is called). The drm core currently does not call pci_enable_device() when a framebuffer driver (including vesafb) is active. If a proper framebuffer driver (e.g., radeonfb) is used, drm still works fine, because the framebuffer driver calls pci_enable_device() itself, and drm gets proper pdev->irq. However, when drm is used together with vesafb, pci_enable_device() is not performed, and the IRQ problem shows up. This patch makes the drm core call pci_enable_device() even if a framebuffer driver was loaded before; this fixes the IRQ problem. --- drm: fix IRQ problem when used together with vesafb Even if drm uses old PCI probing (because a framebuffer driver is active), it still needs to call pci_enable_device() to get correct IRQ. Signed-off-by: Sergey Vlasov <[EMAIL PROTECTED]> ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
