We should try it. As soon as the toolchain is finished and uploaded we will go further. Then more people can help us.
We should try it. As soon as the toolchain is finished and uploaded we will go further. Then more people can help us.
You are making a toolchain for the new kernel with libc?Originally Posted by 4@@@@
@sattommy
My build set up is Debian over VMWare.
Here is the link to download preinstalled Debian image
hxxp://www.visoracle.com/vm/debian50/debian-lenny-50-vmware.zip
And after you boot it up in VMWare, set this line
deb http://www.emdebian.org/debian/ lenny main
in /etc/apt/sources.list.
Then go to Synaptic Package Manager and on the left select http://www.emdebian.org/debian/, you will see list of all precompiled toolchains for many CPUs. I am using mipsel*4.3* versions of gcc,g++, etc ...
Regarding MICOM, I dont know if we can use this. I dont have more details infos for Azbox MICOM so I can compare.
Ok thnx for the info. Installing the VM toolchain as of now. Already booted up my elite with your kernel. I am doing this remotely, as I am not at home this weekend.
I will try and work on the IR/VFD thingie,however don't get any hopes up as I am just starting with the whole c++ stuff. Maybe we can use lirc to see the remote control as serial device, or maybe the micom driver source from kathi is similar to azbox.
@The_Ripper:
This works with HDMI on my Premium
export LD_LIBRARY_PATH=/MMP/lib_old:$LD_LIBRARY_PATH
./set_outports -digital -f HDMI_720p50 -hdmi_chip SiI9030 0 14 15 100 0
insmod em8634GFX.ko
./fb_test /dev/fb0
720x576, 32bpp
Fix alignment 0x17540e40 -> 0x2ac9ce40.
I now see the circles on HDMI.
@Sattommy: We have a toolchain for the original build with uclibc and gcc3.4. But it should be not that big problem to adapt it for the new things which The_ripper uses. We only have to wait until our expert is back.
Last edited by 4@@@@; 06-06-2010 at 03:29 PM.
How did you get the fixed uclib librries in your set_outport file? Did you change this in the makefile?
@sattommy
Yes I added option to the linker to point to folder where is Uclibc libs are. Reads this
hxxp://linux.die.net/man/1/ld, and look at "-rpath dir " option.
Ok thnx. Will try it later. I am working on lirc now. I compiled a simple serial port monitor app, and let is listen on the serial port while killing ir_control. And it neatly shows all commands send by remote control. I am going to setup libc compiler now and see if I can get lirc compiled.
As we need kernel sources to compile lirc_serial kernel module. Could you maybe compile it?
@sattommy
Ok, I will try, anyway I use kernel source for Sigma from
hxxp://download.wdc.com/gpl/WDTV_Live_GPL_code_package.1.01.2 4.zip
So if you want to try something on kernel ...
Regarding lirc, can you tell me what version should I try to compile ?
Well debian mips includes lirc_0.8.3-3_mipsel
I am able to use these binaries on your compiled kernel. They also include sources to build the kernel module.
Thnx for the link to the sources, downloading them now. I am thinking of user the debian on azbox install for compilation, do you think this would work?
It would work, but speed ?
Yeah you are right. It probably will be really slow. For the remote controll. It seems after stracing and monitoring the serial port that the vfd is seperate from the infrared eye. The infrared eyse seems to be a simple one way thingie which sends the rc commands to /dev/ttys1
Monitoring the serial port with a sniffer shows these codes. From which the last number resembles the button pressed.
Now there are three options as to make driverCode:Device --> <DC1> (017) <ENQ> (005) ñ (241) <NUL> (000) <BEL> (007) Device --> <DC1> (017) <ENQ> (005) <SOH> (001) <BS> (008) <US> (031) Device --> <DC1> (017) <ENQ> (005) ñ (241) <BS> (008) <SI> (015) Device --> <DC1> (017) <ENQ> (005) <SOH> (001) <ENQ> (005) <FS> (028) Device --> <DC1> (017) <ENQ> (005) ñ (241) <ENQ> (005) <FF> (012) Device --> <DC1> (017) <ENQ> (005) <SOH> (001) + (043) B (066)
1) write a pipe to grep the numbers and put it to enigma (really dirty way)
2) compile lircd serial module and hope he will be able to work with the azbox
3) write a c++ module/driver which opens serial port and feeds to enigma. or to a node from which enigma reads.
For options two and three there are enigma sources available. Qbox works with lirc, and athi works with their own ir node.
I will try my best this week to make any of these work. But if someone else with better coding skills can pick this up it would probably be much neater.
The_ripper, are you still working on the frambuffer driver? or maybe dvbapi?
just want to say, keep up the good work guys. whatever comes from you is good.
Frame buffer is finished but it needs alot of testing ,so maybe few tweaks in future is needed. I dont know.The_ripper, are you still working on the frambuffer driver? or maybe dvbapi?
It will be hard for you to work/test alone, that's why I stopped working. I dont have any support, no any SVN/GIT server with E2 code that will be patched and worked on, no testing team,no programmer team with knowledge in C++,Python etc ...
@hfmls
Dont wait for me ...
Well thats too bad As I don't have the required skills to pursue this alone.
What I could do however if you want is try and do as much as possible to support you. Things like remote control is doable for me. I guess.
I could setup a git/svn.
Gather some testing people, I myself have one box I can certainly test on full time.
Write up installation guide/scripts to install the stuff on azbox.
but before putting anymore energy in a project like this:
ripper do you think you can manage to write dvbapi?
--I am sure other drivers can be written by other people, however dvbapi is the most difficult.
Are there any other coders in this thread?
--4@@@@ what exactly are you skills?
Cheers,
Tommy
@sattommy
No problem for me to join the group (if any in future)and continue writing low level drivers.
LOL still no E2 then eh!?
GIVE UP PEOPLE
buy a new box.
@ManikM,
Still haven't found a new hobby ?
STOP NAGGIN" !
@ the others;
Keep up the good work, it's really interesting.
@sattommy and The_Ripper. You know where more people will help and noone will write stuff like ManikM.
As I wrote we are preparing the toolchain in git. It tooks some time, because our expert has less time at the moment.
I have a long linux knowledge - since 1994. I'm able to read and modify c or cc code, but I have not that amount of time.
We have some good coders who will be able to help us.
Go on with your work. I will start with vfd in the next few days.
Posting Permissions
Reply With Quote
Bookmarks