I checked in a fix that switches from
dev->pdev->driver->name
to
drm->driver->pci_driver.name
This should fix the segfaults in stealth mode when the pci driver is
set to the wrong driver (fbdev) or no driver (vesafb).
Please give it a try.
--
Jon Smirl
[EMAIL PROTECTED]
-
On Wed, 20 Oct 2004 00:40:07 -0400, Jon Smirl <[EMAIL PROTECTED]> wrote:
> Does this fix it for you? I haven't figured out how to trigger it yet.
I think the problem here is that vesafb is not attached as a true
device driver but it has the resources allocated. DRM comes along and
see vesafb so it
Does this fix it for you? I haven't figured out how to trigger it yet.
[EMAIL PROTECTED] drm-bk]$ bk -r diffs -u
= linux-core/drm_drv.c 1.11 vs edited =
--- 1.11/linux-core/drm_drv.c 2004-10-18 22:58:26 -04:00
+++ edited/linux-core/drm_drv.c 2004-10-20 00:33:20 -04:00
@@ -329,6 +329,8 @
Am Di, den 19.10.2004 schrieb Jon Smirl um 20:11:
> The fault is in drm_set_busid. It's a NULL pointer reference. I'm not
> seeing this so it may be savage specific. The only place I can see
> where you could get a NULL reference is if the PCI driver didn't set a
> name, dev->pdev->driver->name. Ca
What do I have to do to X to make it call set_busid? It's not getting
called in my config.
--
Jon Smirl
[EMAIL PROTECTED]
---
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us wh
The fault is in drm_set_busid. It's a NULL pointer reference. I'm not
seeing this so it may be savage specific. The only place I can see
where you could get a NULL reference is if the PCI driver didn't set a
name, dev->pdev->driver->name. Can you add a debug statement and check
if there is one? The
I noticed some kernel oopses in DRM in my kernel log. They don't seem to
be fatal as DRI is still working. This is on a machine with Vesa
framebuffer. On the other box without kernel framebuffer there are no
oopses.
Oct 19 18:30:31 trabant kernel: [drm] Initialized savage 1.0.0 20011023 on minor 0
