![]() |
|
Cross-compiling 4.4 on ARM |
Luiz Cressoni
Member #12,317
October 2010
![]() |
Hi all, I successfully compiled 4.4 n an ARM platform running linux, but I am unable to make it run. Using the default (empty) allegro.cfg file, allegro_init() returns -1. The only video driver is fb and it is configured correctly. Any hint on where shall I start looking for the problem? Regards,
|
Thomas Fjellstrom
Member #476
June 2000
![]() |
Try printing out the allegro_error variable (its a string). It should say what went wrong. Also, compile allegro in debug mode and look for a file called allegro.log. -- |
Luiz Cressoni
Member #12,317
October 2010
![]() |
Thomas: I found out that I built allegro with WANT_LINUX_CONSOLE=no and WANT_MODULES=yes. Now, it is set_gfx_mode that is crashing. I followed the code and found that it is unable to open a console. /* Get the state of the console -- in particular, the free VT field */ I'm trying to find out why. On the ARM board, I have /dev/tty1 up to /dev/tty63, and /dev/console also.
|
Thomas Fjellstrom
Member #476
June 2000
![]() |
If you find out, please let us know. The linux console support is not well supported or tested these days. -- |
Luiz Cressoni
Member #12,317
October 2010
![]() |
I was able to go a little deeper, and what I found out is that for some reason, /dev/console does not work on this board. So, forcing the code to seek for a /dev/tty%d apparently worked, but the code is freezing on seteuid(). Commenting the command, if goes crazy while 'fork'ing and detaching the processes. I'll take a look on the linux kernel to see some details, since the console is not printing on the lcd screen (although I was able to send some graphics to the framebuffer). I guess that it doesn't open a default console or something like that. I'll post the news when I get any. Regards, --------------------------------- I had to 'hack' some code, but I now can use graphics. The problem is due to some differences between a regular PC and an embedded board. getty 38400 tty1 & Now, I'm trying to make the mouse works. It's a lcd touchscreen, found on /dev/event0 Calls to "has_event(fd, EV_KEY, BTN_MOUSE)" always returns false. Bypassing the check on open_mouse_device, the pointer works (some calibration neeeded, but ok) but there is no 'mouse click'. Seems that the events doesn't have the same code. BTN_MOUSE=0x110 and I tested all events and it starts on 0x800 up to 0xfee on this touchpanel. Connecting an USB mouse, it opens a /dev/event1 and it works perfectly, however.
|
|