lkml.org 
[lkml]   [2009]   [Feb]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: viafb triggers BUG at mm/vmalloc.c:294 [kernel 2.6.28.3]
From
Okay, I did this:

/* for dual-fb must viafb_SAMM_ON=1 and viafb_dual_fb=1 */
if (!viafb_SAMM_ON)
viafb_dual_fb = 0;

DEBUG_MSG(KERN_INFO "before first ioremap\n");

/* Set up I2C bus stuff */
viafb_create_i2c_bus(viaparinfo);

viafb_init_chip_info();
viafb_get_fb_info(&viaparinfo->fbmem, &viaparinfo->memsize);
viaparinfo->fbmem_free = viaparinfo->memsize;
viaparinfo->fbmem_used = 0;
viaparinfo->fbmem_virt = ioremap_nocache(viaparinfo->fbmem,
viaparinfo->memsize);
viafbinfo->screen_base = (char *)viaparinfo->fbmem_virt;

if (!viaparinfo->fbmem_virt) {
printk(KERN_INFO "ioremap failed\n");
return -1;
}

DEBUG_MSG(KERN_INFO "after first ioremap\n");

viafb_get_mmio_info(&viaparinfo->mmio_base, &viaparinfo->mmio_len);
viaparinfo->io_virt = ioremap_nocache(viaparinfo->mmio_base,
viaparinfo->mmio_len);

DEBUG_MSG(KERN_INFO "after second ioremap\n");

It was the first one indeed. Full dmesg and config attached.

--
wixor
[unhandled content-type:application/octet-stream][unhandled content-type:application/octet-stream]
\
 
 \ /
  Last update: 2009-02-07 22:47    [from the cache]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and my Meterkast|Read the blog