Started by tmcdos, July 04, 2015, 09:42:06 pm
Quote from: swahren on July 05, 2015, 06:30:44 pmProviding a Windows Executable is pretty unusual for Linux sources. Looks suspicious to me.
Quote from: tmcdos on July 05, 2015, 07:42:23 pmI am not sure what do you mean. There is no executable file in the archive - only textual information (besides the DTB, but you can always compile it from the DTS).If you are talking about choosing ZIP instead of GZ or XZ or even TAR - I can not see a strong enough reason why to prefer one over another, they are all equally suitable for the purpose.
Quote from: swahren on July 06, 2015, 01:12:42 amIf i click on your link above then i'll get an imx233_0.zip.exe
Quote from: tmcdos on July 05, 2015, 07:42:23 pmRegarding sending the patches upstream - I am still quite new to this forum and to the hardware platform itself, and do not know what is the procedure.
Quote I do not need a credit, just wanted to share a working solution for a specific problem.
bus = 0xb83d34c8
Kernel panic - not syncing: Requested init /usr/lib/systemd/systemd failed (error -2).CPU: 0 PID: 1 Comm: swapper Not tainted 4.1.4-ARCH #9Hardware name: Freescale MXS (Device Tree)[<c000ef4c>] (unwind_backtrace) from [<c000cf0c>] (show_stack+0x10/0x14)[<c000cf0c>] (show_stack) from [<c03fdb20>] (panic+0x98/0x200)[<c03fdb20>] (panic) from [<c03fca7c>] (kernel_init+0x80/0xec)[<c03fca7c>] (kernel_init) from [<c000a3b0>] (ret_from_fork+0x14/0x24)---[ end Kernel panic - not syncing: Requested init /usr/lib/systemd/systemd failed (error -2).
without your actual Kernel config and used bootloader it would be hard to find the problem.