+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: Linux (https://forum.kodi.tv/forumdisplay.php?fid=52)
+---- Thread: Android help, j1nx source code (/showthread.php?tid=187570)
help, j1nx source code - kentiger - 2014-02-26
hi, does anyone knows where can have the source code for j1nx linux xbmc (for MIDNIGHT M3), manufacturer now changed the WIFI moudel, anybody know how to amend to make it suitable for the new wifi module
tks
RE: help, j1nx source code - davilla - 2014-02-26
ask j1nx, they made it not us.
RE: help, j1nx source code - Ned Scott - 2014-02-27
If I had to guess: https://github.com/j1nx
RE: help, j1nx source code - kentiger - 2014-02-27
many thanks,
(2014-02-27, 03:19)Ned Scott Wrote: If I had to guess: https://github.com/j1nx
RE: help, j1nx source code - kentiger - 2014-02-27
`/home/ubuntu/MBXildroot-AmLogic-master/package/config'
package/thirdparty/Config.in:32: can't open file "package/thirdparty/rtmpdump/Config.in"
make: *** [amlogic_f16ref-xbmc_defconfig] 错误 1
RE: help, j1nx source code - davilla - 2014-02-27
and that an XBMC problem because ?
Seriously, file an issue on their github. It's their distro and they are responsible for it.
RE: help, j1nx source code - kentiger - 2014-02-27
thanks
(2014-02-27, 07:08)davilla Wrote: and that an XBMC problem because ?
Seriously, file an issue on their github. It's their distro and they are responsible for it.
RE: help, j1nx source code - j1nx - 2014-02-27
Somebody rang?
RE: help, j1nx source code - davilla - 2014-02-27
* davilla points ^^
RE: help, j1nx source code - kentiger - 2014-02-28
dear j1nx, can u do the favor? and now have the patch, we can send to you.
many thanks
(2014-02-27, 20:00)j1nx Wrote: Somebody rang?
RE: help, j1nx source code - dhead - 2014-02-28
@kentiger
You might want to use CronicCorey Buildroot tree which is much more updated, Corey already added support to M3, look at https://github.com/CoreTech-Development/buildroot-mx_linux/blob/2013.11-Amlogic/configs/mx_linux_xiosm3_defconfig (though you might need to adapt the ref16 config from https://github.com/J1nx-Hackable-Gadgets/buildroot-AmLogic/blob/master/configs/amlogic_f16ref_gbox-xbmc_defconfig )
Also the XBMC tree of CronicCorey is updated and works great with M3 (I already tried it with J1nx buildroot tree).
Kernel wise, I believe you'll need to enable the "Realtek EU series (8188EU 8188ETV) Wireless USB Dongle support (NEW)" module in the kernel, this one might be included only in the latest kernel sources of Amlogic, See https://github.com/j1nx/Openlinux.Amlogic.M3
RE: help, j1nx source code - j1nx - 2014-02-28
As it is indeed one happy family, I updated the M3 stuff for TLBB towards the same 2013.11 buildroot code as the MX one. This code has been flow back to Corey's branch where he has start supporting the xios on that code.
Without knowing exactly which wifi driver you have troubles with, I suspect you ended up with a M3 board design with a rtl8188EU wifi. The original rtl8188CU within the earlier boxes is discontinued by realtek, but the rtl8188ETV as replacement runs on the same driver so should just work. The 8188EU indeed does not work correctly with the CU driver. It basically only requires you to change the wifi driver within the defconfig file from the 8188CUS to the 8188EU and recompile.
RE: help, j1nx source code - kentiger - 2014-03-01
many thanks,
(2014-02-28, 12:39)dhead Wrote: @kentiger
You might want to use CronicCorey Buildroot tree which is much more updated, Corey already added support to M3, look at https://github.com/CoreTech-Development/buildroot-mx_linux/blob/2013.11-Amlogic/configs/mx_linux_xiosm3_defconfig (though you might need to adapt the ref16 config from https://github.com/J1nx-Hackable-Gadgets/buildroot-AmLogic/blob/master/configs/amlogic_f16ref_gbox-xbmc_defconfig )
Also the XBMC tree of CronicCorey is updated and works great with M3 (I already tried it with J1nx buildroot tree).
Kernel wise, I believe you'll need to enable the "Realtek EU series (8188EU 8188ETV) Wireless USB Dongle support (NEW)" module in the kernel, this one might be included only in the latest kernel sources of Amlogic, See https://github.com/j1nx/Openlinux.Amlogic.M3
dear j1nx
tks for your commetns, and also thanks for your efforts on the M3 chip.
now i have got the patch , need to change wext into nl80211 inside the patch also, but the guy who made the patch does not know how to compile it, shall i send you the patch, and then you can compile it and have one new upgrading file.
tks again.
quote='j1nx' pid='1640089' dateline='1393617924']
As it is indeed one happy family, I updated the M3 stuff for TLBB towards the same 2013.11 buildroot code as the MX one. This code has been flow back to Corey's branch where he has start supporting the xios on that code.
Without knowing exactly which wifi driver you have troubles with, I suspect you ended up with a M3 board design with a rtl8188EU wifi. The original rtl8188CU within the earlier boxes is discontinued by realtek, but the rtl8188ETV as replacement runs on the same driver so should just work. The 8188EU indeed does not work correctly with the CU driver. It basically only requires you to change the wifi driver within the defconfig file from the 8188CUS to the 8188EU and recompile.
[/quote]
RE: help, j1nx source code - kentiger - 2014-03-01
it is 8188etv
RE: help, j1nx source code - j1nx - 2014-03-02
(2014-03-01, 05:14)kentiger Wrote: now i have got the patch , need to change wext into nl80211 inside the patch also, but the guy who made the patch does not know how to compile it, shall i send you the patch, and then you can compile it and have one new upgrading file.
tks again.
Let me start with; How on earth can someone make a patch, but don't know how to compile
Secondly; the 2.6.34.x kernel does not support nl80211. The wifi driver has some >2.6.37 <2.6.39 support if needed, but you really should go up to 2.6.39. As we are using 2.6.34.14 (or 15), patching the driver to nl80211 is not doing you any good.
Actually, we stepped away from the in-xbmc way of configuring the network and instead, implemented the more "normal" linux way using NetworkManager (wext based) and the a bit older NetworkManager xbmc plugin.
Anyway, if it is a ETV, it should just work on the same CUS driver.