Firefly Open Source Community

   Login   |   Register   |
New_Topic

Mali kernel driver TX011-SW-99002-r5p1-00rel0 for firefly

10

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
10
Posted at 3/5/2015 15:40:40     

Re: Mali kernel driver TX011-SW-99002-r5p1-00rel0 for firefly

Has anyone managed managed to get DRM compiled in the kernel, I'm getting errors.
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 3/17/2015 00:35:16     
Wouldn't it be just possible to backup your whole partitions via Rkflashtool?
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 3/17/2015 02:47:37     
At least for Windows theres an easy dump tool:
http://forum.xda-developers.com/ ... p-firmware-t2915363
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 4/24/2015 10:54:54     
hi busybee! what's the kernel version you use?3.10.0 or other? thanks!
Reply

Use props Report

12

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
12
Posted at 4/27/2015 16:20:37     
busybee Posted at 3/2/2015 18:21
Yes, ganggangstyle-en, there's a kernel crash after resume from screen suspend

Hi! busybee ! "Yes, ganggangstyle-en, there's a kernel crash after resume from screen suspend"
Do you have solved it?
Reply

Use props Report

6

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
6
Posted at 6/11/2015 06:26:06     
Hello all... I'm hoping someone can help me out.

I have built the stock kernel (https://bitbucket.org/T-Firefly/firefly-rk3288-kernel.git) and imported the Mali userspace binaries into my rootfs.  I'm trying to launch weston with the fbdev backend, but I get an error:


  1. [12:01:21.889] weston 1.4.0
  2.                http://wayland.freedesktop.org/
  3.                Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.4.0
  4.                Build: 6d359c5-dirty Fixed issue with processing position on touch up. (2014-12-11 16:46:13 -0800)
  5. [12:01:21.890] OS: Linux, 3.10.0, #1 SMP PREEMPT Mon Jun 8 16:34:54 PDT 2015, armv7l
  6. [12:01:21.890] Using config file '/etc/xdg-config/default/weston.ini'
  7. [12:01:21.890] Loading module '/usr/lib/weston/fbdev-backend.so'
  8. [12:01:21.892] initializing fbdev backend
  9. [12:01:21.892] Creating fbdev output.
  10. [12:01:21.892] Opening fbdev frame buffer.
  11. [12:01:21.892] Calculating pixman format from:
  12.                 - type: 0 (aux: 0)
  13.                 - visual: 2
  14.                 - bpp: 32 (grayscale: 0)
  15.                 - red: offset: 24, length: 8, MSB: 0
  16.                 - green: offset: 16, length: 8, MSB: 0
  17.                 - blue: offset: 8, length: 8, MSB: 0
  18.                 - transp: offset: 0, length: 8, MSB: 0
  19. [12:01:21.892] Mapping fbdev frame buffer.
  20. [12:01:21.892] Failed to mmap frame buffer: Invalid argument
  21. [12:01:21.892] Mapping frame buffer failed.
  22. [12:01:21.893] fatal: failed to create compositor
Copy the code


So I thought I'd try to 'dd' some random data into the framebuffer:


  1. # dd if=/dev/random of=/dev/fb0 bs=512 count=32
  2. dd: writing '/dev/fb0': No such device
  3. 0+1 records in
  4. 0+0 records out
  5. 0 bytes (0 B) copied, 0.000217584 s, 0.0 kB/s
Copy the code


The device node exists:


  1. # ls -l /dev/fb*
  2. crw-rw-rw- 1 root video 29, 0 Jan  1 12:00 /dev/fb0
  3. crw-rw-rw- 1 root video 29, 1 Jan  1 12:00 /dev/fb1
  4. crw-rw-rw- 1 root video 29, 2 Jan  1 12:00 /dev/fb2
  5. crw-rw-rw- 1 root video 29, 3 Jan  1 12:00 /dev/fb3
  6. crw-rw-rw- 1 root video 29, 4 Jan  1 12:00 /dev/fb4
Copy the code


But there seems to be some disconnect in the kernel between this device node and the backing driver.

I've also tried launch X with the fbdev driver, but I get a similar error:


  1. [1098091.703] (II) LoadModule: "fbdev"
  2. [1098091.704] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
  3. [1098091.705] (II) Module fbdev: vendor="X.Org Foundation"
  4. [1098091.705]   compiled for 1.14.2, module version = 0.4.4
  5. [1098091.705]   Module class: X.Org Video Driver
  6. [1098091.705]   ABI class: X.Org Video Driver, version 14.1
  7. [1098091.705] (II) FBDEV: driver for framebuffer: fbdev
  8. [1098091.705] (++) using VT number 7
  9. [1098091.705] (WW) Falling back to old probe method for fbdev
  10. [1098091.705] (II) Loading sub module "fbdevhw"
  11. [1098091.705] (II) LoadModule: "fbdevhw"
  12. [1098091.705] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
  13. [1098091.706] (II) Module fbdevhw: vendor="X.Org Foundation"
  14. [1098091.706]   compiled for 1.14.99.1, module version = 0.0.2
  15. [1098091.706]   ABI class: X.Org Video Driver, version 14.1
  16. [1098091.707] (II) FBDEV(0): using default device
  17. [1098091.707] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
  18. [1098091.707] (**) FBDEV(0): Depth 24, (--) framebuffer bpp 32
  19. [1098091.707] (==) FBDEV(0): RGB weight 888
  20. [1098091.707] (==) FBDEV(0): Default visual is TrueColor
  21. [1098091.707] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
  22. [1098091.707] (II) FBDEV(0): hardware: fb0 (video memory: 0kB)
  23. [1098091.707] (II) FBDEV(0): checking modes against framebuffer device...
  24. [1098091.707] (II) FBDEV(0):    mode "1280x720" ok
  25. [1098091.707] (II) FBDEV(0): checking modes against monitor...
  26. [1098091.707] (--) FBDEV(0): Virtual size is 1280x720 (pitch 1280)
  27. [1098091.707] (**) FBDEV(0):  Mode "1280x720": 74.2 MHz (scaled from 0.0 MHz), 45.0 kHz, 59.9 Hz
  28. [1098091.707] (II) FBDEV(0): Modeline "1280x720"x0.0   74.18  1280 1390 1430 1650  720 725 730 750 +hsync +vsync (45.0 kHz)
  29. [1098091.707] (==) FBDEV(0): DPI set to (96, 96)
  30. [1098091.707] (II) Loading sub module "fb"
  31. [1098091.707] (II) LoadModule: "fb"
  32. [1098091.708] (II) Loading /usr/lib/xorg/modules/libfb.so
  33. [1098091.712] (II) Module fb: vendor="X.Org Foundation"
  34. [1098091.712]   compiled for 1.14.99.1, module version = 1.0.0
  35. [1098091.712]   ABI class: X.Org ANSI C Emulation, version 0.4
  36. [1098091.712] (**) FBDEV(0): using shadow framebuffer
  37. [1098091.713] (II) Loading sub module "shadow"
  38. [1098091.713] (II) LoadModule: "shadow"
  39. [1098091.713] (II) Loading /usr/lib/xorg/modules/libshadow.so
  40. [1098091.715] (II) Module shadow: vendor="X.Org Foundation"
  41. [1098091.715]   compiled for 1.14.99.1, module version = 1.1.0
  42. [1098091.715]   ABI class: X.Org ANSI C Emulation, version 0.4
  43. [1098091.715] (==) Depth 24 pixmap format is 32 bpp
  44. [1098091.715] (EE) FBDEV(0): mmap fbmem: Invalid argument
  45. [1098091.715] (EE) FBDEV(0): mapping of video memory failed
  46. [1098091.715] (EE)
  47. Fatal server error:
  48. [1098091.715] (EE) AddScreen/ScreenInit failed for driver 0
  49. [1098091.715] (EE)
  50. [1098091.715] (EE)
Copy the code


The X log seems to think that the fb0 device has 0kB of video memory.  This might explain why the mmap fails for both weston and X.

Does anyone have any ideas why the stock kernel isn't working for me with the fbdev driver?

Thanks!
Reply

Use props Report

693

Credits

0

Prestige

0

Contribution

advanced

Rank: 4

Credits
693
Posted at 9/4/2015 04:30:37     
Kernel Device Driver r7p0-02rel0        21 August 2015
http://malideveloper.arm.com/res ... nel-device-drivers/

someone tried to integrate the new driver into the kernel?
Reply

Use props Report

25

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
25
Posted at 9/14/2015 19:41:23     
Hello All,
Has anybody tried using mali with armsoc driver for X11 rendering. I tried using r4p0 drivers without success.
Thanks!!
Reply

Use props Report

14

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
14
Posted at 9/16/2015 22:44:16     
Ava Posted at 3/3/2015 18:02
>>Error: eglGetError(): 12289 (0x3001)
  >>Error: Failed to initialize EGL at ../../../../samples ...

i have the same problem,do you know how to deal with it?  thanks
Reply

Use props Report

14

Credits

0

Prestige

0

Contribution

new registration

Rank: 1

Credits
14
Posted at 9/16/2015 22:47:49     
busybee Posted at 3/4/2015 18:20
thanks, right now there is no /dev/mali

mali_kbase is loaded and the fbdev drivers are present in ...

I have the mali_kbase module and the mali0 but I have the error   

Error: eglGetError(): 12289 (0x3001)

Error: Failed to initialize EGL at src/EGLRuntime.cpp:245
how to deal with it
Reply

Use props Report

You need to log in before you can reply Login | Register

This forum Credits Rules

Quick Reply Back to top Back to list