That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!
Regards,
That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!
Regards,
config-3.12.5-bone10.4 (111 KB)
Hi Robert,
Not necessary. Your V3.12 is booting via NFS. Just needed to enable
CONFIG_ROOT_NFS =y. I¹m surprised that more developers don¹t use NFS.
I
can make all the file changes directly on my desktop and simply hit
the
reset button and viola I¹m up and running. No need to program SDCards.
Also, I have my targetNFS automated backup every hour so if I get into
trouble, I can got back to a previous version in seconds.BTW, when the kernel is configured for Initrd, NFS doesn¹t work, so I
was
wondering why your kernel is configured to use Initrd. Is this really
necessary?We need it to support the Netinstall.
GitHub - RobertCNelson/netinstall: Network Install for a bunch of arm boardsThe debian-installer is contained within in a custom initrd, that we
run at startup, which is then used to create the rest of the root
disk..Good to know.
BTW, good news is SGX is working on your kernel. I can run the 3D demos
under /opt/gfxsdkdemos/ogles2.I¹m using 3.12.5-bone.4
Thank you again for all your help.
That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!
Hi Robert,
BTW, how difficult would it be to get SGX working on your V3.8 kernel? Iām
using Xenomai and currently there is no Xenomai patch for V3.12.
Regards,
John
That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!Hi Robert,
BTW, how difficult would it be to get SGX working on your V3.8 kernel? Iām
using Xenomai and currently there is no Xenomai patch for V3.12.
We will find out tomorrow..
The main thing was to get it working on a mainline 3.12 first, as "ti
claims it works" so next comes the 3.8 madness... So we will see
tomorrow/friday...
Regards,
That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!Hi Robert,
BTW, how difficult would it be to get SGX working on your V3.8 kernel?
I¹m
using Xenomai and currently there is no Xenomai patch for V3.12.We will find out tomorrow..
The main thing was to get it working on a mainline 3.12 first, as "ti
claims it works" so next comes the 3.8 madness... So we will see
tomorrow/friday...
Fantastic. You are the greatest.
Thank you so much,
John
That's awesome news, btw can you please attach your config, i kinda
went hack-happy since .4 with the base config. Plus yours works!Hi Robert,
BTW, how difficult would it be to get SGX working on your V3.8 kernel?
I¹m
using Xenomai and currently there is no Xenomai patch for V3.12.We will find out tomorrow..
The main thing was to get it working on a mainline 3.12 first, as "ti
claims it works" so next comes the 3.8 madness... So we will see
tomorrow/friday...
Hi Robert,
I see that sgx_build_modules.sh isn¹t working. I¹ll work on fixing the
problem?
Regards,
John
Hi Robert,
I see that sgx_build_modules.sh isn¹t working. I¹ll work on fixing the
problem?
Other then building the modules, I'm not sure anything else is correct yet.
Regards,
btw, I'd like to really integrate the sgx driver into the staging
tree, like we did in the 2.6.32 day's, then end users only have to run
a script on x86 to extrace the important bits, no kernel module
building.. (you can see my hacks in the sgx-blob directory..)
Regards,
Hi Robert,
I see that sgx_build_modules.sh isn¹t working. I¹ll work on fixing the
problem?Other then building the modules, I'm not sure anything else is correct
yet.
No problem. Iāll fix it for you.
Hi Robert,
I see that sgx_build_modules.sh isn¹t working. I¹ll work on fixing the
problem?Other then building the modules, I'm not sure anything else is correct
yet.btw, I'd like to really integrate the sgx driver into the staging
tree, like we did in the 2.6.32 day's, then end users only have to run
a script on x86 to extrace the important bits, no kernel module
building.. (you can see my hacks in the sgx-blob directory..)
Yeah, I saw that last night. Excellent idea.
BTW, it looks like you missed the Kbuild patch in
services4/3rdparty/linux_drm/Kbuild
Regards,
John
That change is actually buried in the initial 5.00.00.01 commit, i
need to refactor that change back out..
Regards,
Hi Robert,
I see that sgx_build_modules.sh isn¹t working. I¹ll work on fixing
the
problem?Other then building the modules, I'm not sure anything else is correct
yet.btw, I'd like to really integrate the sgx driver into the staging
tree, like we did in the 2.6.32 day's, then end users only have to run
a script on x86 to extrace the important bits, no kernel module
building.. (you can see my hacks in the sgx-blob directory..)Yeah, I saw that last night. Excellent idea.
BTW, it looks like you missed the Kbuild patch in
services4/3rdparty/linux_drm/KbuildThat change is actually buried in the initial 5.00.00.01 commit, i
need to refactor that change back out..
Ah, now I see what youāre doing. OK, so the patched Kbuild is in
ignore/ti-sdk-pvr/Graphics_SDK/GFX_Linux_KM/service4/3rdparty/linux_drm/Kbu
ild
Why donāt you just update make.rules and then "make x x x", "make x x x
install" like normal?
That change is actually buried in the initial 5.00.00.01 commit, i
need to refactor that change back out..
Hi Robert,
I don¹t seem to be making the modules you are. I have attached my SGX make
log.
My make commands are:
make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 all install
BTW, your build is failing when it builds drm, but my build doesn¹t build
drm.
When I run QT applications, I use the eglfs platform.
Regards,
John
MakeSGXLog.txt (84.3 KB)
That change is actually buried in the initial 5.00.00.01 commit, i
need to refactor that change back out..Hi Robert,
I don¹t seem to be making the modules you are. I have attached my SGX make
log.My make commands are:
make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 all install
Hi Robert,
Yep, that was the problem. If you look at Prathap Srinivas E2E post on Nov
5, he doesnāt use xorg support. I change the make line in your script, and
now it builds without error.
Regards,
John
That change is actually buried in the initial 5.00.00.01 commit, i
need to refactor that change back out..Hi Robert,
I don¹t seem to be making the modules you are. I have attached my SGX
make
log.My make commands are:
make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 all installHi Robert,
Yep, that was the problem. If you look at Prathap Srinivas E2E post on Nov
5, he doesnāt use xorg support. I change the make line in your script, and
now it builds without error.
Hi Robert,
So, line 602 should read:
build_sgx_modules release 8.x no 0 1 all
Regards,
John
make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 all installHi Robert,
Yep, that was the problem. If you look at Prathap Srinivas E2E post on Nov
5, he doesnāt use xorg support. I change the make line in your script, and
now it builds without error.Hi Robert,
So, line 602 should read:
build_sgx_modules release 8.x no 0 1 all
yeap, but that sucks, was hoping it would be more useful.. Maybe in
the next release. At least qt/eglfs users can use it.
Or if the lxde -> lxde-qt port would finish.
Regards,
make BUILD=release OMAPES=8.x PM_RUNTIME=1 all
sudo make BUILD=release OMAPES=8.x PM_RUNTIME=1 all installHi Robert,
Yep, that was the problem. If you look at Prathap Srinivas E2E post on
Nov
5, he doesn¹t use xorg support. I change the make line in your script,
and
now it builds without error.Hi Robert,
So, line 602 should read:
build_sgx_modules release 8.x no 0 1 allyeap, but that sucks, was hoping it would be more useful.. Maybe in
the next release. At least qt/eglfs users can use it.
That is all I needed for now, so I¹m happy, but if this worked on 3.8, I
would be even more happy.
yeap, but that sucks, was hoping it would be more useful.. Maybe in
the next release. At least qt/eglfs users can use it.Or if the lxde -> lxde-qt port would finish.
I didn¹t know about this. Looks great. I wonder if they are using wayland?
Hello,
since you guys seems to well know the BBB I would like to know if it is possible to compile Qt5.2 for angstrom distribution or do I have to install the TI SQK ?
Thanks for your help.