I have setup a build environment for OpenPLI 3.0. After some initial problems it builds.
Now I would like to make a small change to openpli/enigma2/lib/dvb/demux.cpp
How and where do I make that local change in my build environment?
I'm a total newbie building using bitbake so please forgive me if the question is stupid. I can take that :-) as long as you give me a pointer in the right direction.
- Magnus
Want to test a change in demux.cpp - How is that done?
Started by sirwio, 08 Feb 2013 23:13
7 replies to this topic
Re: Want to test a change in demux.cpp - How is that done? #2
Re: Want to test a change in demux.cpp - How is that done? #3
Re: Want to test a change in demux.cpp - How is that done? #4
Posted 9 February 2013 - 01:12
also you can use "diff -u" for a file or "diff -Naur" for a folder and add the patch to bb file as SRC_URI
Open Vision sources: https://github.com/OpenVisionE2
Re: Want to test a change in demux.cpp - How is that done? #5
Posted 8 March 2013 - 07:46
If id like to do change to demux.cpp do I have to compile whole image or can I just use some hexeditor to do change?
I just want to change
As i do have issues with it and I´d like to test if it will fix my problems.
Using Vu Solo2 which has 1024MB memory.
I just want to change
result = 20; // 512MB systems: Use 4MB IO buffers (et9x00, vuultimo, ...)to
result = 40; // 512MB systems: Use 4MB IO buffers (et9x00, vuultimo, ...)
As i do have issues with it and I´d like to test if it will fix my problems.
Using Vu Solo2 which has 1024MB memory.
[eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eFilePushThreadRecorder] WRITE ERROR, aborting thread [eDVBRecordFileThread] waiting for aio to complete [eDVBRecordFileThread] Waiting for I/O to complete main thread is non-idle! display spinner! [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB) 0: 29 1: 7407 2: 7096 3: 1 4: 1 5: 1 6: 1 7: 1 8: 1 9: 1 10: 1 11: 1 [eDVBRecordFileThread] Waiting for I/O to complete 12: 1 13: 1 14: 1 15: 1 16: 1 17: 1 18: 1 19: 1 20: 1 [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] Waiting for I/O to complete [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] wait: aio_return returned failure: Interrupted system call [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB) 0: 19 1: 3683 2: 3536 3: 1 4: 1 5: 1 6: 1 7: 1 8: 1 9: 1 10: 1 11: 1 12: 1 13: 1 14: 1 15: 1 16: 1 17: 1 18: 1 19: 1 20: 1 [eFilePushThreadRecorder] THREAD STOP [eFilePushThreadRecorder] THREAD STOP
Re: Want to test a change in demux.cpp - How is that done? #6
Re: Want to test a change in demux.cpp - How is that done? #7
Posted 8 March 2013 - 15:45
If id like to do change to demux.cpp do I have to compile whole image or can I just use some hexeditor to do change?
I just want to changeresult = 20; // 512MB systems: Use 4MB IO buffers (et9x00, vuultimo, ...)toresult = 40; // 512MB systems: Use 4MB IO buffers (et9x00, vuultimo, ...)As i do have issues with it and I´d like to test if it will fix my problems.
It probably won't. The buffer size is NOT your problem, otherwise you'd see more than a single overun event.
Real musicians never die - they just decompose
Re: Want to test a change in demux.cpp - How is that done? #8
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users