Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread William Hermans
On Tue, Oct 4, 2016 at 6:05 PM, Matthijs van Duin wrote: > On 5 October 2016 at 02:43, William Hermans wrote: > >> So libEGL is Mesa's Wayland extensions. >> > > No. > > >

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Matthijs van Duin
On 5 October 2016 at 02:43, William Hermans wrote: > So libEGL is Mesa's Wayland extensions. > No. https://en.wikipedia.org/wiki/EGL_(API) > Mesa is a 3d graphics library. Not sure how SGX even comes in at this > context ? > > Well it's not going to if you accidently use

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread William Hermans
On Tue, Oct 4, 2016 at 12:24 PM, Matthijs van Duin < matthijsvand...@gmail.com> wrote: > On Wednesday, 28 September 2016 11:05:50 UTC+2, Matteo Facchinetti wrote: >> >> libEGL warning: DRI3: xcb_connect failed >> libEGL warning: DRI2: xcb_connect failed >> libEGL warning: DRI2: xcb_connect failed

Re: [beagleboard] Re: init-eMMC-flasher mmcqd allocation failures

2016-10-04 Thread William Hermans
No idea if either of you 'flash' many devices at once. But it would be good to be 100% sure where, and why this issue occurs. I have not experienced this issue at all. But quite honestly I think I've flashed the eMMC of only 3 different boards a few times each. In each case, rsync work

Re: [beagleboard] Re: init-eMMC-flasher mmcqd allocation failures

2016-10-04 Thread William Hermans
> > Instead of deferring until memory is available, or even just proceeding > without DMA, the omap_hsmmc driver immediately fails the request with an > error, thus pretty much guaranteeing loss of data or even filesystem > corruption. I personally think this is completely unacceptable behaviour

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Robert Nelson
On Tue, Oct 4, 2016 at 5:23 PM, Matthijs van Duin wrote: > On 4 October 2016 at 23:18, Robert Nelson wrote: >> >> debian@beaglebone:~$ sudo modprobe pvrsrvkm >> >> (nothing in dmesg) >> >> debian@beaglebone:~$ lsmod | grep pvr >> pvrsrvkm

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Matthijs van Duin
On 4 October 2016 at 23:18, Robert Nelson wrote: > > debian@beaglebone:~$ sudo modprobe pvrsrvkm > > (nothing in dmesg) > > debian@beaglebone:~$ lsmod | grep pvr > pvrsrvkm 379674 0 > debian@beaglebone:~$ ls /dev/dri/* > /dev/dri/card0 /dev/dri/controlD64 >

[beagleboard] Re: [beaglebone] Help on rootfs encryption for Beaglebone Green

2016-10-04 Thread Sylvain Lamontagne
Hi Robert, I put some debug output in the scripts (enormous script 0_0) and it seems that when it creates the loop device to associate with device-mapper for the rootfs it's giving it only 2MB. The rootfs is certainly not going to fit in it. :) Sylvain -- For more options, visit

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Robert Nelson
On Tue, Oct 4, 2016 at 3:34 PM, Matthijs van Duin wrote: > On Monday, 26 September 2016 21:06:17 UTC+2, RobertCNelson wrote: >> >> sudo mkdir -p /lib/modules/4.4.11-00332-gce54280-dirty/extra/ >> sudo ln -s /lib/modules/`uname -r`/extra/ti335x/pvrsrvkm.ko >>

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Matthijs van Duin
On Monday, 26 September 2016 21:06:17 UTC+2, RobertCNelson wrote: > > sudo mkdir -p /lib/modules/4.4.11-00332-gce54280-dirty/extra/ > sudo ln -s /lib/modules/`uname -r`/extra/ti335x/pvrsrvkm.ko > /lib/modules/4.4.11-00332-gce54280-dirty/extra/pvrsrvkm.ko > You can also just modprobe the module

[beagleboard] Re: [beaglebone] Help on rootfs encryption for Beaglebone Green

2016-10-04 Thread Sylvain Lamontagne
+beaglebone as it was the original thread Hi Robert, I may be doing something wrong, but following exactly what you proposed result in a lot of "Cannot mkdir: No space left on device" and "Cannot open: No such file or directory" while the script populate_rootfs. The last displayed line is "tar:

[beagleboard] Re: [beaglebone] Help on rootfs encryption for Beaglebone Green

2016-10-04 Thread Sylvain Lamontagne
Ok I'll try this. Thank you Sylvain On Tue, Oct 4, 2016 at 3:10 PM, Robert Nelson wrote: > On Tue, Oct 4, 2016 at 11:23 AM, Sylvain Lamontagne > wrote: > > Hi Robert, > > > > thank you for your answer. > > I've tried what you proposed,

Re: [beagleboard] SGX on 4.4.*-ti-rt kernel

2016-10-04 Thread Matthijs van Duin
On Wednesday, 28 September 2016 11:05:50 UTC+2, Matteo Facchinetti wrote: > > libEGL warning: DRI3: xcb_connect failed > libEGL warning: DRI2: xcb_connect failed > libEGL warning: DRI2: xcb_connect failed > Unable to initialise egl > egl error 'EGL_NOT_INITIALIZED' (0x3001) > > Sounds like

[beagleboard] Re: [beaglebone] Help on rootfs encryption for Beaglebone Green

2016-10-04 Thread Robert Nelson
On Tue, Oct 4, 2016 at 11:23 AM, Sylvain Lamontagne wrote: > Hi Robert, > > thank you for your answer. > I've tried what you proposed, but it seems the script doesn't like it when > it tries to rsync the files. > I've added a set -x here is the relevant output: > +

[beagleboard] Re: init-eMMC-flasher mmcqd allocation failures

2016-10-04 Thread Matthijs van Duin
I've also run into this once during an apt-get upgrade, leaving the system in a pretty hosed state. I managed to recover it but it required a lot of effort. Although evidently rare, this is clearly a very serious issue. The direct cause is edma_prep_slave_sg() failing to allocate memory for the

Re: [beagleboard] Re: Trouble with capacitive touch panel GT911 which does not work upon power-up but works after restart.

2016-10-04 Thread Robert Nelson
On Tue, Oct 4, 2016 at 7:01 AM, wrote: > I am pretty sure that the problem is in the following block of code: > interrupts = <8 13 2>; > irq-gpios = <8 13>; > reset-gpios = <8 14>; > > I do not know how to define these

[beagleboard] I2C Chip not detected

2016-10-04 Thread Charles
Hi, I'm having some issue trying to talk to a chip over I2C. The chip in question is the ATAES132 (https://cdn.sparkfun.com/datasheets/Dev/Beagle/Atmel-8760-CryptoAuth-ATAES132-Datasheet.pdf) on the cryptocape. Up to yesterday I could send command and read response packets from the Command

[beagleboard] Recent Debian (4.4.21-ti-r47): RALINK MT7601 not working

2016-10-04 Thread pbft
I've been using a Mediatek USB wi-fi adapter with a BBB for quite a while. In upgrading to the more-or-less latest Robert Nelson kernel, I can't get it to work. It appears that there's now kernel support for the 7601 chipset - I see a driver module at

[beagleboard] Re: Trouble with capacitive touch panel GT911 which does not work upon power-up but works after restart.

2016-10-04 Thread libor . orgovan . nt
I am pretty sure that the problem is in the following block of code: *interrupts * *= <8 13 2>; irq-gpios = <8 13>; reset-gpios = <8 14>;* I do not know how to define these gpios in that block of code, how to assign them to

[beagleboard] what means "voltage normalized" for AIO READ?

2016-10-04 Thread Rva
In http://iotdk.intel.com/docs/master/mraa/aio_8h.html I read that *mraa_aio_read_float* is a *voltage normalized 0.0f - 1.0f * so I have 0.5 as the value , I must multiply with 1.8 on a beaglebone ? -- For more options, visit http://beagleboard.org/discuss --- You received this message

[beagleboard] Building BBGW from source

2016-10-04 Thread drhunter95
Hi, Is there a page documenting the BBGW build process? I'm assuming https://eewiki.net/display/linuxonarm/BeagleBone+Black does not cover it as BBGW is not listed as an available board. Thanks, Iain -- For more options, visit http://beagleboard.org/discuss --- You received this message