Dear DRI mailing list, I'm trying to make my Radeon Mobility M300 (probably PCIE) which is reported as
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Radeon Mobility M300] work with the EGL demos. This is because I'd like to help out with EGL +MESA development. Now I'm totally stuck, and suppose I hit a few deeply-rooted problems that I cannot solve without in-depth knowledge about DRM memory layout. DRI/Mesa are fresh GIT checkouts, I also had this problem with old CVS builds. Such knowledge doesn't seem to be available publicly, and understanding the details often requires one to have much previous knowledge about graphic achitectures in general - which I suppose is often NDAed, as the publicly available papers aren't too long. Feel free to prove me wrong, I'm really interested in understanding GART, FB, VRAM, shared memory, the DRM locking scheme and especially how they play together. Back to my kernel panic: My DRM debugging output is [17199560.604000] [drm:radeon_do_init_cp] [17199560.604000] [drm:radeon_do_init_cp] dev_priv->cp_ring->handle e1cf5000 [17199560.604000] [drm:radeon_do_init_cp] dev_priv->ring_rptr->handle e1df6000 [17199560.608000] [drm:radeon_do_init_cp] dev->agp_buffer_map->handle e1df7000 [17199560.608000] [drm] Setting GART location based on old memory map [17199560.608000] [drm:radeon_do_init_cp] dev_priv->gart_size 8388608 [17199560.608000] [drm:radeon_do_init_cp] dev_priv->gart_vm_start 0x4000000 [17199560.612000] [drm:radeon_do_init_cp] dev_priv->gart_buffers_offset 0x4102000 [17199560.612000] [drm:radeon_do_init_cp] Setting phys_pci_gart to 00000000 07FF8000 [17199560.612000] [drm:drm_ati_pcigart_init] PCI: Gart Table: VRAM 07FF8000 mapped at 00000000 [17199560.612000] BUG: unable to handle kernel NULL pointer dereference at virtual address 00000000 (...) The last two lines really look fishy. The basic problem seems to be that in radeon_do_init_cp(), the drm_core_ioremap(&dev_priv->gart_info.mapping, dev); fails, i.e. the mapping's handle is NULL afterwards. I have no clue what's causing this. Maybe there has to be added special code for dealing with PCIE cards that use shared memory. I'm really stuck here, thanks for any hints! -- Christian Neumair <[EMAIL PROTECTED]> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
