2009-03-03 06:31:41     Kernel-Panic with nano-X and Epson S1D13513 Framebufferdevice

Document created by Aaronwu Employee on Aug 14, 2013
Version 1Show Document
  • View in full screen mode

2009-03-03 06:31:41     Kernel-Panic with nano-X and Epson S1D13513 Framebufferdevice

Michael Heiser (GERMANY)

Message: 70278   

 

Hey guys,

 

I got my S1D13513 working on Blackfin. The driver is loading correctly (I think). But when i want to start nano-X i got a kernel-panic! It seems that the driver has a problem with mm/nommu.c. I will now attach the bootlog. Perhaps anyone can help me with this problem, cause I have no experience in driver development.

 

Regards,

 

Michael

 

bugreport.txt

TranslateQuoteReplyEditDelete

 

 

2009-03-03 06:36:56     Re: Kernel-Panic with nano-X and Epson S1D13513 Framebufferdevice

Michael Heiser (GERMANY)

Message: 70279   

 

The file I attached is the wrong one! Here is the right one.

 

Regards,

 

Michael

 

bugreport.txt

TranslateQuoteReplyEditDelete

 

 

2009-03-03 06:58:38     RE: Re: Kernel-Panic with nano-X and Epson S1D13513 Framebufferdevice

Michael Hennerich (GERMANY)

Message: 70281    In s1d13513fb_mmap()

 

Change vma->vm_flags

to

vma->vm_flags |= VM_MAYSHARE | VM_SHARED;

 

and try again.

 

 

QuoteReplyEditDelete

 

 

2009-03-03 09:35:12     RE: Re: Kernel-Panic with nano-X and Epson S1D13513 Framebufferdevice

Michael Heiser (GERMANY)

Message: 70290   

 

In s1d13513fb_mmap()

 

Change vma->vm_flags

to

vma->vm_flags |= VM_MAYSHARE | VM_SHARED;

 

and try again.

 

 

---

 

Very good! The driver is working but I still don't see anything on my display...

 

But I think that is a Hardwareproblem which i have to fix....

 

Regards Michael

Attachments

    Outcomes