[beagleboard] Re: Debian Stretch + Kernel arm 4.4.76-bone-rt-r18 - missing insserv

[Moscowbob]

Thanks Robert

On Saturday, 8 July 2017 09:16:50 UTC+1, Moscowbob wrote:
>
> Hi All,
>
> I have just followed the instructions for building kernel + sgx modules 
> and the sgx drivers were not installed after reboot.
> Going through the /opt/gfxinstall/sgx-install.sh script I found that 
> /sbin/insserv was not installed. After installing the package and reboot 
> all is fine.
>
> Can somebody please confirm that this is the correct solution and that I 
> did not have some other mistake in producing the sd card according to these 
> instruction
>
> https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SGX
>
> Thanks 
> Rob
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d228a9f1-1322-46c2-9c6c-d2105b9752b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Debian Stretch + Kernel arm 4.4.76-bone-rt-r18 - missing insserv

[Moscowbob]

Hi All,

I have just followed the instructions for building kernel + sgx modules and 
the sgx drivers were not installed after reboot.
Going through the /opt/gfxinstall/sgx-install.sh script I found that 
/sbin/insserv was not installed. After installing the package and reboot 
all is fine.

Can somebody please confirm that this is the correct solution and that I 
did not have some other mistake in producing the sd card according to these 
instruction

https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SGX

Thanks 
Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/99fb0685-bb4f-4dd2-b890-ec545f08d373%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Kernel 4.4.31-bone-rt-r14 sgx-startup.sh - not setting permissions

[Moscowbob]

After spending some time with systemd and udec documentation and playing 
with udevadm I managed to find a solution.
No need to modify the sgx-startup.sh script, I just added a permission a 
sgx-permissions.rule to /etc/udev/rules.d with the folowing line 
- SUBSYSTEM=="pvr", GROUP="video", MODE="0660".

I am not sure, maybe somebody can clarify - I think the chmod 666 
/dev/pvrsrvkm has no effect since when modprobe is called, kernel and udev 
events will trigger and the default permissions for udev on devices is 600.

Regards

Rob


On Tuesday, 29 November 2016 15:46:28 UTC, Moscowbob wrote:
>
> After hours of reading all sorts and my brain blowing up, I think I might 
> have found the reason for the problem. However, as a Linux noob, I am now 
> stuck and hope one of our gurus will shed light on this.
>
> This is where I am now:
>
> 1. Copied the "start" section of sgx-startup.sh to a new file and started 
> fiddling.
> 2. Found that there appears to be some delay between modprobe pvrsrvkm , 
> deleting the /dev/pvrsrvkm file and what I assume is the kernel module 
> setting permissions on the file.
> 3. When I moved the delete and mknod to after the /usr/local/bin/pvrsrvctl 
> --start --no-module and added a sleep 1, the file permissions were set 
> correctly.
>
> Unfortunately this only work when I run the script manually, it doe not 
> work with reboot (maybe sleep cannot be used)
>
> So, I am still trying to find a solution, but I am running out of things 
> to try 
>
> Thanks
>
> Rob
>
> On Sunday, 27 November 2016 21:59:06 UTC, Moscowbob wrote:
>>
>>
>> I have just built fresh kernel, dtb, u-boot and sgx as per RCN eewiki 
>> <https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel>
>>  and 
>> I have also built Qt 5.6.2.
>> Everything is working correctly except for one problem which I do not 
>> understand and hope somebody could explain.
>>
>> After installing sgx drivers and a reboot I have everything as per 
>> instructions:
>>
>> lsmod | grep omaplfb
>>
>> omaplfb12356  0 
>> tilcdc 26717  1 omaplfb
>> pvrsrvkm  157212  1 omaplfb
>>
>> but my Qt Quick programs only work when run as root (sudo).
>>
>> Looking at the sgx-startup script, /dev/pvrsvrkm should be set with 666 
>> permissions, but after startup this is what I get:
>> ls -al /dev/pvrsrvkm 
>> crw--- 1 root root 247, 0 Nov 27 20:54 /dev/pvrsrvkm
>>
>> When I run:
>> sudo /etc/init.d/sgx-startup.sh stop
>> sudo /etc/init.d/sgx-startup.sh start
>>
>> I get:
>> sgx: Starting PVR
>> /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=129)
>>  
>> ls -al /dev/pvrsrvkm 
>> crw-rw-rw- 1 root root 247, 0 Nov 27 21:48 /dev/pvrsrvkm
>> Permissions are now correct for running program as normal user.
>>
>> my programs run correctly with platform eglfs - which is what I want.
>>
>> My questions:
>>
>> 1. Why does sgx-startup.sh not set the permissions correctly on boot and 
>> is there a way to solve this?
>>
>> Thanks in advance
>>
>> Rob
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7a87b2ed-140d-4674-9e83-5bb598618b6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Kernel 4.4.31-bone-rt-r14 sgx-startup.sh - not setting permissions

[Moscowbob]

After hours of reading all sorts and my brain blowing up, I think I might 
have found the reason for the problem. However, as a Linux noob, I am now 
stuck and hope one of our gurus will shed light on this.

This is where I am now:

1. Copied the "start" section of sgx-startup.sh to a new file and started 
fiddling.
2. Found that there appears to be some delay between modprobe pvrsrvkm , 
deleting the /dev/pvrsrvkm file and what I assume is the kernel module 
setting permissions on the file.
3. When I moved the delete and mknod to after the /usr/local/bin/pvrsrvctl 
--start --no-module and added a sleep 1, the file permissions were set 
correctly.

Unfortunately this only work when I run the script manually, it doe not 
work with reboot (maybe sleep cannot be used)

So, I am still trying to find a solution, but I am running out of things to 
try 

Thanks

Rob

On Sunday, 27 November 2016 21:59:06 UTC, Moscowbob wrote:
>
>
> I have just built fresh kernel, dtb, u-boot and sgx as per RCN eewiki 
> <https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-LinuxKernel>
>  and 
> I have also built Qt 5.6.2.
> Everything is working correctly except for one problem which I do not 
> understand and hope somebody could explain.
>
> After installing sgx drivers and a reboot I have everything as per 
> instructions:
>
> lsmod | grep omaplfb
>
> omaplfb12356  0 
> tilcdc 26717  1 omaplfb
> pvrsrvkm  157212  1 omaplfb
>
> but my Qt Quick programs only work when run as root (sudo).
>
> Looking at the sgx-startup script, /dev/pvrsvrkm should be set with 666 
> permissions, but after startup this is what I get:
> ls -al /dev/pvrsrvkm 
> crw--- 1 root root 247, 0 Nov 27 20:54 /dev/pvrsrvkm
>
> When I run:
> sudo /etc/init.d/sgx-startup.sh stop
> sudo /etc/init.d/sgx-startup.sh start
>
> I get:
> sgx: Starting PVR
> /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=129)
>  
> ls -al /dev/pvrsrvkm 
> crw-rw-rw- 1 root root 247, 0 Nov 27 21:48 /dev/pvrsrvkm
> Permissions are now correct for running program as normal user.
>
> my programs run correctly with platform eglfs - which is what I want.
>
> My questions:
>
> 1. Why does sgx-startup.sh not set the permissions correctly on boot and 
> is there a way to solve this?
>
> Thanks in advance
>
> Rob
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/34bbc924-70f6-49cf-96f1-f758a802d29d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel 4.4.31-bone-rt-r14 sgx-startup.sh - not setting permissions

[Moscowbob]

This is confusing me even more now - I added a "stat" on /dev/pvrsrvkm in 
the sgx-startup.sh, at the end before the "start" finishes and the 
permissions areset correctly -
debian@arm:~$ systemctl status sgx-startup
● sgx-startup.service - LSB: Start daemon at boot time
   Loaded: loaded (/etc/init.d/sgx-startup.sh; generated; vendor preset: 
enabled
   Active: active (exited) since Mon 2016-11-28 07:37:30 UTC; 1min 59s ago
 Docs: man:systemd-sysv-generator(8)
   CGroup: /system.slice/sgx-startup.service

Nov 28 07:37:27 arm systemd[1]: Starting LSB: Start daemon at boot time...
Nov 28 07:37:27 arm sgx-startup.sh[363]: sgx: Starting PVR
Nov 28 07:37:30 arm systemd[1]: Started LSB: Start daemon at boot time.
Nov 28 07:37:30 arm sgx-startup.sh[363]: 666  <<<<< just before the script 
completes

debian@arm:~$ ls -al /dev/pvrsrvkm 
crw--- 1 root root 247, 0 Nov 28 07:37 /dev/pvrsrvkm

but still the permissions are 600 as can be seen above.
Any advice will be greatly appreciated.

Thanks

Rob

On Sunday, 27 November 2016 23:16:25 UTC, Moscowbob wrote:
>
> Thank you Robert but I am  not sure what you mean, would you kindly 
> clarify.
> As far as I understand the script, you are setting the permissions to 666 
> and you also start the service.
> What I do not understand is how and why the permissions are not set when 
> the script runs in the first place.
>
> Rob
>
> On Sunday, 27 November 2016 22:03:50 UTC, RobertCNelson wrote:
>>
>> On Sun, Nov 27, 2016 at 3:59 PM, Moscowbob <mosc...@gmail.com> wrote: 
>> > 
>> > I have just built fresh kernel, dtb, u-boot and sgx as per RCN eewiki 
>> and I 
>> > have also built Qt 5.6.2. 
>> > Everything is working correctly except for one problem which I do not 
>> > understand and hope somebody could explain. 
>> > 
>> > After installing sgx drivers and a reboot I have everything as per 
>> > instructions: 
>> > 
>> > lsmod | grep omaplfb 
>> > 
>> > omaplfb12356  0 
>> > tilcdc 26717  1 omaplfb 
>> > pvrsrvkm  157212  1 omaplfb 
>> > 
>> > but my Qt Quick programs only work when run as root (sudo). 
>> > 
>> > Looking at the sgx-startup script, /dev/pvrsvrkm should be set with 666 
>> > permissions, but after startup this is what I get: 
>> > ls -al /dev/pvrsrvkm 
>> > crw--- 1 root root 247, 0 Nov 27 20:54 /dev/pvrsrvkm 
>> > 
>> > When I run: 
>> > sudo /etc/init.d/sgx-startup.sh stop 
>> > sudo /etc/init.d/sgx-startup.sh start 
>> > 
>> > I get: 
>> > sgx: Starting PVR 
>> > /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) 
>> (err=129) 
>> > 
>> > ls -al /dev/pvrsrvkm 
>> > crw-rw-rw- 1 root root 247, 0 Nov 27 21:48 /dev/pvrsrvkm 
>> > Permissions are now correct for running program as normal user. 
>> > 
>> > my programs run correctly with platform eglfs - which is what I want. 
>> > 
>> > My questions: 
>> > 
>> > 1. Why does sgx-startup.sh not set the permissions correctly on boot 
>> and is 
>> > there a way to solve this? 
>>
>> Oh let's patch that in the sgx-startup.sh script..  Probably after the 
>> modprobe/pvrsrvct start.. 
>>
>> Send me a patch and i'll push it out... 
>>
>> Regards, 
>>
>> -- 
>> Robert Nelson 
>> https://rcn-ee.com/ 
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/71145c6e-6aa9-43f0-a8c4-190b314fc38e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Kernel 4.4.31-bone-rt-r14 sgx-startup.sh - not setting permissions

[Moscowbob]

Thank you Robert but I am  not sure what you mean, would you kindly clarify.
As far as I understand the script, you are setting the permissions to 666 
and you also start the service.
What I do not understand is how and why the permissions are not set when 
the script runs in the first place.

Rob

On Sunday, 27 November 2016 22:03:50 UTC, RobertCNelson wrote:
>
> On Sun, Nov 27, 2016 at 3:59 PM, Moscowbob <mosc...@gmail.com 
> > wrote: 
> > 
> > I have just built fresh kernel, dtb, u-boot and sgx as per RCN eewiki 
> and I 
> > have also built Qt 5.6.2. 
> > Everything is working correctly except for one problem which I do not 
> > understand and hope somebody could explain. 
> > 
> > After installing sgx drivers and a reboot I have everything as per 
> > instructions: 
> > 
> > lsmod | grep omaplfb 
> > 
> > omaplfb12356  0 
> > tilcdc 26717  1 omaplfb 
> > pvrsrvkm  157212  1 omaplfb 
> > 
> > but my Qt Quick programs only work when run as root (sudo). 
> > 
> > Looking at the sgx-startup script, /dev/pvrsvrkm should be set with 666 
> > permissions, but after startup this is what I get: 
> > ls -al /dev/pvrsrvkm 
> > crw--- 1 root root 247, 0 Nov 27 20:54 /dev/pvrsrvkm 
> > 
> > When I run: 
> > sudo /etc/init.d/sgx-startup.sh stop 
> > sudo /etc/init.d/sgx-startup.sh start 
> > 
> > I get: 
> > sgx: Starting PVR 
> > /usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) 
> (err=129) 
> > 
> > ls -al /dev/pvrsrvkm 
> > crw-rw-rw- 1 root root 247, 0 Nov 27 21:48 /dev/pvrsrvkm 
> > Permissions are now correct for running program as normal user. 
> > 
> > my programs run correctly with platform eglfs - which is what I want. 
> > 
> > My questions: 
> > 
> > 1. Why does sgx-startup.sh not set the permissions correctly on boot and 
> is 
> > there a way to solve this? 
>
> Oh let's patch that in the sgx-startup.sh script..  Probably after the 
> modprobe/pvrsrvct start.. 
>
> Send me a patch and i'll push it out... 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/74c4aefa-8147-4508-a1ef-39b54229bfdb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Kernel 4.4.31-bone-rt-r14 sgx-startup.sh - not setting permissions

[Moscowbob]

I have just built fresh kernel, dtb, u-boot and sgx as per RCN eewiki 

 and 
I have also built Qt 5.6.2.
Everything is working correctly except for one problem which I do not 
understand and hope somebody could explain.

After installing sgx drivers and a reboot I have everything as per 
instructions:

lsmod | grep omaplfb

omaplfb12356  0 
tilcdc 26717  1 omaplfb
pvrsrvkm  157212  1 omaplfb

but my Qt Quick programs only work when run as root (sudo).

Looking at the sgx-startup script, /dev/pvrsvrkm should be set with 666 
permissions, but after startup this is what I get:
ls -al /dev/pvrsrvkm 
crw--- 1 root root 247, 0 Nov 27 20:54 /dev/pvrsrvkm

When I run:
sudo /etc/init.d/sgx-startup.sh stop
sudo /etc/init.d/sgx-startup.sh start

I get:
sgx: Starting PVR
/usr/local/bin/pvrsrvctl: SrvInit failed (already initialized?) (err=129)
 
ls -al /dev/pvrsrvkm 
crw-rw-rw- 1 root root 247, 0 Nov 27 21:48 /dev/pvrsrvkm
Permissions are now correct for running program as normal user.

my programs run correctly with platform eglfs - which is what I want.

My questions:

1. Why does sgx-startup.sh not set the permissions correctly on boot and is 
there a way to solve this?

Thanks in advance

Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e16f3de9-fe79-4438-b77e-109ee13c1c19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Serial MARK/SPACE parity - Timing

[Moscowbob]

Greetings All,

I would appreciate some advice on the following problem-
I need to communicate with and industrial device using the "9th bit high" 
protocol, which means the address byte is sent with parity set to mark and 
all other bytes sent with parity set to space.
I have implemented this and the parity setting is working correctly.
However, when switching over from MARK parity to SPACE parity using the 
tcsetattr, the delay between first(address) byte and the next byte 
following is +- 20ms. 
This is way out of the protocol spec of max inter-byte delay of 5ms.

What would be the best approach to to reducing this timing?
Will it be possible with the 8250omap driver which uses dma?

Any other tips, pointers will be appreciated.

Thanks
Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Correct way t grant user permission to /dev/fb0 and /dev/input/event1

[Moscowbob]

Right, Google did not yield any direct answers but a few pointers here and 
there.
After messing up my rootfs a couple of times trying different things, I am 
back to square one.
I have discovered that although the debian user is member of video and 
input groups, it only helps in terms of running ts_calibrate and ts_test 
programs, launching any qt 5.5 program with eglfs, just terminates with 
failure message that egl could not be initialized - there is no message 
about permissions or anything else (like running a system command without 
sudo, you get a command not found error)

Launching program with sudo actually runs the program but with various 
warnings about environment variables that need to be set in order for qt to 
know the physical screen size.
logging in as debian and doing su, then launching program, everything works 
100%, no errors, warnings or anything else.
So in my limited knowledge of linux, i have come to the conclusion that all 
the problems above are due to permissions.

1. How can I determine where the permission failure is happening?
2. How would I grant the correct permissions for user debian to be able 
to run the qt program

Any advice, pointers, thoughts would be greatly appreciated.

Thanks

Rob



On Thursday, 6 August 2015 21:39:27 UTC+1, William Hermans wrote:

 The immediate thing to do, if not done already would be to google the 
 exact error message. This may, or may not give you an answer to your 
 problem.

 Indeed adding your user to a group in this case seems like the real way 
 to go. So preferable if you can nail down this issue.

 On Thu, Aug 6, 2015 at 1:18 PM, Moscowbob mosc...@gmail.com javascript:
  wrote:

 Thanks for the replies gents I have opted for Barry's suggestion and just 
 added the user to input group for /dev/event1, for fb0, the user is member 
  of viseo group by default.
 This seemed to work when testing with ts_calibrate and ts_test - works 
 withou sudo but, when trying to rung a QT5 program with eglfs, it fails 
 with cannot initialise.
 However, when running as sudo, the program works - I assume thewre are 
 further permission problems somewhere so further insight or help will be 
 greatly appreciated.

 Thabks

 Rob


 On Monday, 3 August 2015 21:19:32 UTC+1, Barry Day wrote:

 For /dev/fb0 use addgroup to add your user to the video group

 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google Groups 
 BeagleBoard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to beagleboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] nfs boot - no ssh keys

[Moscowbob]

Thanks Robert,

Looking at the chroot.sh script in omap-image-builder, I see that that you 
copy this file to /etc/init.d/generic-boot-script.sh for Wheezy and Ubuntu 
but this is not done for Jessie/Stretch.
I have a custom cape and once this is installed I do not have access to 
serial debug cable, so having ssh run from the start is important for me.

All your scripts are installed in /opt so would it work if I just copy the 
script to /etc/init.d/ after I untar the the rootfs to nfs dir ?

Thank you for your work and support.

Rob

On Monday, 3 August 2015 14:48:59 UTC+1, RobertCNelson wrote:

 On Mon, Aug 3, 2015 at 4:05 AM, Moscowbob mosc...@gmail.com javascript: 
 wrote: 
  Hello, 
  My network boot and nfs are all working but I cannot ssh into the BBB. 
  Looking in /etc/ssh there are no ssh_host* files - there are a few files 
 and 
  a ssh_regenerate. 
  
  Rootfs: 
  ./RootStock-NG.sh -c eewiki_minfs_debian_jessie_armhf 
  
  kernel: 
  kernel_version=3.14.48-ti-r72 
  
  /etc/fstab 
  debugfs /sys/kernel/debug debugfs defaults 0 0 
  
  Do I need any scripts or configuration to enable the the regeneration of 
 the 
  ssh keys on first boot ? 

 Normally this script gets called on bootup: 


 https://github.com/RobertCNelson/boot-scripts/blob/master/boot/generic-startup.sh#L8
  

 so just: 

 sudo dpkg-reconfigure openssh-server 

 Regards, 

 -- 
 Robert Nelson 
 https://rcn-ee.com/ 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] nfs boot - no ssh keys

[Moscowbob]

Decided to update and rebuild - saw you already changed it :)

Busy building now - thanks

On Monday, 3 August 2015 17:09:45 UTC+1, RobertCNelson wrote:

 On Mon, Aug 3, 2015 at 11:04 AM, Robert Nelson robert...@gmail.com 
 javascript: wrote: 
  On Mon, Aug 3, 2015 at 10:57 AM, Moscowbob mosc...@gmail.com 
 javascript: wrote: 
  Thanks Robert, 
  
  Looking at the chroot.sh script in omap-image-builder, I see that that 
 you 
  copy this file to /etc/init.d/generic-boot-script.sh for Wheezy and 
 Ubuntu 
  but this is not done for Jessie/Stretch. 
  
  Yeah that was moved to bb-customizations... 
  
  Here's the systemd file.. 
  
  
 https://github.com/RobertCNelson/omap-image-builder/blob/master/target/init_scripts/systemd-generic-board-startup.service
  
  
  I should check and see if bb-customizations is in the deb package 
  line and add the above when not.. 
  
  I have a custom cape and once this is installed I do not have access to 
  serial debug cable, so having ssh run from the start is important for 
 me. 
  
  All your scripts are installed in /opt so would it work if I just copy 
 the 
  script to /etc/init.d/ after I untar the the rootfs to nfs dir ? 
  
  Yeap.. just copy: 
  
  
 https://raw.githubusercontent.com/RobertCNelson/omap-image-builder/master/target/init_scripts/systemd-generic-board-startup.service
  
  
  to: /lib/systemd/system/ 
  
  and 
  
  sudo  systemctl enable systemd-generic-board-startup.service 

 fixed going forward: 


 https://github.com/RobertCNelson/omap-image-builder/commit/6f5a0dfad65fbed091d2687fdb1e1d58e7c8bbf8
  

 Regards, 

 -- 
 Robert Nelson 
 https://rcn-ee.com/ 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Correct way t grant user permission to /dev/fb0 and /dev/input/event1

[Moscowbob]

I have cross compiled QT 5.5.0 for the BBB with debian jessie rootfs and 
3.14-ti kernel (both latest)
I can run examples using eglfs but need to do so using sudo.
I would like to run these directly from the default debian user.

My questions are:
1. What is the correct method of granting access to the devices required?
2. Will this work to launch application remotely via ssh? 

Any advice or pointers will be appreciated.

Thanks

Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] nfs boot - no ssh keys

[Moscowbob]

Hello,
My network boot and nfs are all working but I cannot ssh into the BBB. 
Looking in /etc/ssh there are no ssh_host* files - there are a few files 
and a ssh_regenerate.

Rootfs:
./RootStock-NG.sh -c eewiki_minfs_debian_jessie_armhf

kernel:
kernel_version=3.14.48-ti-r72

/etc/fstab
debugfs /sys/kernel/debug debugfs defaults 0 0 

Do I need any scripts or configuration to enable the the regeneration of 
the ssh keys on first boot ?

thanks

Rob


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Jesse lxqt, 4.3 CAP lcd - Incorrect mouse cursor

[Moscowbob]

Thank you Robert,
I do not know if this is correct, but since the lightdm.conf has no 
settings enabled in this image, I just copied the lightdm.conf file from 
the lxde image and it is now working. 

On Thursday, 18 December 2014 14:45:15 UTC, RobertCNelson wrote:

 On Thu, Dec 18, 2014 at 4:16 AM, Moscowbob mosc...@gmail.com 
 javascript: wrote: 
  Hello All 
  
  I am need of some help with getting the touch screen working correctly 
 with 
  the below configuration 
  
  BBB Rev C 
  Custom Cape with Newhaven 4.3 capactive touch screen 
  Image: BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2014-11-19-2gb.img 
  Kernel: 3.14.26-ti-r41 
  
  The system boots up and the desktop appears correctly, however, when I 
 touch 
  the screen, the mouse cursor hardly moves, I installed evtest and the 
 touch 
  screen is showing the correct data when different sections of the 
 display is 
  touched. 
  
  I am using the built in kernel driver for edt-ft5x06 chip for touch 
 screen 
  
  How/where do I configure the desktop to use the touch screen as input or 
 use 
  it as a mouse ? 
  Do I need to any additional packages installed in order to achieve this? 

 use: 
 xinput-calibrator 

 Except, i haven't wired it into lightdm to load it by default yet with 
 the Jessie Image. 

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Jesse lxqt, 4.3 CAP lcd - Incorrect mouse cursor

[Moscowbob]

Hello All

I am need of some help with getting the touch screen working correctly with 
the below configuration

BBB Rev C
Custom Cape with Newhaven 4.3 capactive touch screen
Image: BBB-eMMC-flasher-debian-jessie-lxqt-armhf-2014-11-19-2gb.img
Kernel: 3.14.26-ti-r41

The system boots up and the desktop appears correctly, however, when I 
touch the screen, the mouse cursor hardly moves, I installed evtest and the 
touch screen is showing the correct data when different sections of the 
display is touched.

I am using the built in kernel driver for edt-ft5x06 chip for touch screen

How/where do I configure the desktop to use the touch screen as input or 
use it as a mouse ?
Do I need to any additional packages installed in order to achieve this?

Thanks

Rob

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Moscowbob]

@William - After reading RCN explanation that different locations are 
searched, this crossed my mind and I deleted all uEnv.txt files everywhere 
except for the sd card fat partition, but this still does not work if I add 
either 
cmdline=quiet init=/lib/systemd/systemd consoleblank=0
OR
cmdline=quiet init=/lib/systemd/systemd
optarg=consoleblank=0

to the /boot/uEnv.txt on the nfs

My next step was to just use a fat formatted sd card with MLO, uimage and 
uEnv.txt and no ext4 partition and still the same - the consoleblank does 
not work for my configuration if added to /boot/uEnv.txt

Thanks

Rob


On Tuesday, 9 September 2014 05:33:10 UTC+1, William Hermans wrote:

 Jason, he was using a console testing image, and using the built in env 
 variables for tftp + nfs. These images came with two uEnv.txt files, and 
 since he was having problems with uboot env variables I'm betting he 
 actually had 3 uEnv.txt files.

 1) fat / boot part
 2) ext4 footfs on sdcard
 3) ext4 rootfs on nfs share host.

 uboot was probably pulling in the uEnv.txt which he was not editing. Which 
 again, I'm betting was on partition 2 ( ext4 ) of the sdcard. e.g. he was 
 editing the uEnv.txt file on the nfs share as I suggested.

 On Mon, Sep 8, 2014 at 9:04 PM, Robert Nelson robert...@gmail.com 
 javascript: wrote:

 On Mon, Sep 8, 2014 at 10:22 PM, Jason Lange j.b@gmail.com 
 javascript: wrote:
 
 
  On Sun, Sep 7, 2014 at 8:35 PM, William Hermans yyr...@gmail.com 
 javascript: wrote:
 
  Jason, hah ! I see why now. Can you see the problem ?
 
  uname_r=3.15.10-bone8
  cmdline=quiet init=/lib/systemd/systemd
  optargs=consoleblank=0.
 
 
  This is actually in the wrong file. For this to work in the file he's
  using there it needs to be as i said above. Which is:
 
  cmdline=quiet init=/lib/systemd/systemd consoleblank=0
 
  This is because the file he's using is the second stage uEnv.txt file 
 and
  not the one loaded at boot. Which now that I think about it could have 
 very
  well been my problem too.
 
 
  Well I finally understand what your saying here -- I didn't know that 
 there
  are/were two functional uEnv.txts.  This looks like the file that I set 
 my
  optargs in (that is, it starts with the uname_r variable being set), 
 but I
  am running the new set up with only one uEnv.txt being functional.
 
  @Robert again for clarity:
 
  In a setup that only uses one uEnv.txt (that being /boot/uEnv.txt) that 
 is
  the place to set your optargs but in the two functional uEnv.txt setup 
 the
  place to set optargs is /uEnv.txt?

 Just edit:

 /boot/uEnv.txt

 /uEnv.txt is just a shim..

  And if that is so, what is the simplest way for someone to know which 
 of the
  two situations they are dealing with?

 /uEnv.txt will set your bootargs like so:

 setenv bootargs console=tty0 console=\${console} \${optargs}
 \${cape_disable} \${cape_enable} root=/dev/mmcblk0p1
 rootfstype=\${mmcrootfstype} \${cmdline}

 So override any of those \${var} by defining them in /boot/uEnv.txt

 Regards,

 --
 Robert Nelson
 http://www.rcn-ee.com/

 --
 For more options, visit http://beagleboard.org/discuss
 ---
 You received this message because you are subscribed to the Google Groups 
 BeagleBoard group.
 To unsubscribe from this group and stop receiving emails from it, send an 
 email to beagleboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Moscowbob]

Thanks Robert, that clears up things for me now

On Tuesday, 9 September 2014 15:28:20 UTC+1, RobertCNelson wrote:

 On Tue, Sep 9, 2014 at 9:13 AM, Moscowbob mosc...@gmail.com javascript: 
 wrote: 
  @William - After reading RCN explanation that different locations are 
  searched, this crossed my mind and I deleted all uEnv.txt files 
 everywhere 
  except for the sd card fat partition, but this still does not work if I 
 add 
  either 
  cmdline=quiet init=/lib/systemd/systemd consoleblank=0 
  OR 
  cmdline=quiet init=/lib/systemd/systemd 
  optarg=consoleblank=0 
  
  to the /boot/uEnv.txt on the nfs 

 on the nfs u-boot can't read /boot/uEnv.txt off the nfs (yet)... 
 for the nfs case, it's got to be on the first partition /uEnv.txt 

  
  My next step was to just use a fat formatted sd card with MLO, uimage 
 and 
  uEnv.txt and no ext4 partition and still the same - the consoleblank 
 does 
  not work for my configuration if added to /boot/uEnv.txt 

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: optargs in kernel 3.15.10-bone8

[Moscowbob]

Thank you all for you assistance the problem is resolved. just some 
additional points.

SD Card boot partition:
uEnv.txt

##Rename as: uEnv.txt to boot via nfs

##https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

##SERVER: sudo apt-get install tftpd-hpa
##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa
##SERVER: zImage/*.dtb need to be located here:
##SERVER: TFTP_DIRECTORY/zImage
##SERVER: TFTP_DIRECTORY/dtbs/*.dtb

##client_ip needs to be set for u-boot to try booting via nfs

client_ip=192.168.1.17

#u-boot defaults: uncomment and override where needed

server_ip=192.168.1.12
gw_ip=192.168.1.1
netmask=255.255.255.0
#hostname=
device=eth0
#autoconf=off
root_dir=/home/rob/beaglebone/rootfs
nfs_options=,vers=3
nfsrootfstype=ext4 rootwait fixrtc
*optargs=consoleblank=0*



rootfs/boot/
uEnv.txt
---
uname_r=3.15.10-bone8
cmdline=quiet init=/lib/systemd/systemd
*#cmdline=quiet init=/lib/systemd/systemd consoleblank=0  === DOES NOT 
WORK*


Thanks
Rob




On Monday, 8 September 2014 01:15:14 UTC+1, Moscowbob wrote:


 BBB boot from tftp and nfs -
 kernel:  3.15.10-bone8 
 rootfs:  debian-jessie-console-armhf-2014-08-13

 Hardware:
 BBB A5C
 Circuitco LCD4 cape
 Circuitco RS232 cape

 /home/rob/rootfs/boot/uEnv.txt

 uname_r=3.15.10-bone8
 cmdline=quiet init=/lib/systemd/systemd
 *optargs=consoleblank=0*.

 I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ 
 http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F
  but 
 the display is still blanking after 10  minutes.

 Would appreciate some guidance.

 Thanks
 Rob
  



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: optargs in kernel 3.15.10-bone8

[Moscowbob]

Sorry - there is a typo..

.the display is now not blanking, after adding the optargs to uEnv.txt 
in the fat boot partition but for learning sake, I would like to know how 
to achieve this in the /boot/uEnv.txt


On Monday, 8 September 2014 11:08:35 UTC+1, Moscowbob wrote:

 Thanks William, but the line in red is just commented out to indicate it 
 is not part of the working file. I did not work without the hash.
 I have followed these instructions 
 http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0#nfs_support and 
 there is no mention of any netargs..

 Apologies for my ignorance, but I am brand new to all this and having a 
 hard time following, would you please clarify how to achieve what you 
 mentioned.

 the display is now not balnking after adding the optargs to uEnv.txt in 
 the fat boot partition but for learning sake, I would like to know how to 
 achieve this in the /boot/uEnv.txt

 Thanks for the help.

 Rob


 On Monday, 8 September 2014 10:12:14 UTC+1, William Hermans wrote:



 *#cmdline=quiet init=/lib/systemd/systemd consoleblank=0  === DOES 
 NOT WORK*


 That would be because you need to remove the comment . . .remove the 
 hash mark or '#'. If that does not work, then your netargs do not contain 
 ${cmdline}

 On Mon, Sep 8, 2014 at 1:20 AM, Moscowbob mosc...@gmail.com wrote:

 Thank you all for you assistance the problem is resolved. just some 
 additional points.

 SD Card boot partition:
 uEnv.txt
 
 ##Rename as: uEnv.txt to boot via nfs

 ##https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

 ##SERVER: sudo apt-get install tftpd-hpa
 ##SERVER: TFTP_DIRECTORY defined in /etc/default/tftpd-hpa
 ##SERVER: zImage/*.dtb need to be located here:
 ##SERVER: TFTP_DIRECTORY/zImage
 ##SERVER: TFTP_DIRECTORY/dtbs/*.dtb

 ##client_ip needs to be set for u-boot to try booting via nfs

 client_ip=192.168.1.17

 #u-boot defaults: uncomment and override where needed

 server_ip=192.168.1.12
 gw_ip=192.168.1.1
 netmask=255.255.255.0
 #hostname=
 device=eth0
 #autoconf=off
 root_dir=/home/rob/beaglebone/rootfs
 nfs_options=,vers=3
 nfsrootfstype=ext4 rootwait fixrtc
 *optargs=consoleblank=0*

 

 rootfs/boot/
 uEnv.txt
 ---
 uname_r=3.15.10-bone8
 cmdline=quiet init=/lib/systemd/systemd
 *#cmdline=quiet init=/lib/systemd/systemd consoleblank=0  === DOES 
 NOT WORK*
 

 Thanks
 Rob




 On Monday, 8 September 2014 01:15:14 UTC+1, Moscowbob wrote:


 BBB boot from tftp and nfs -
 kernel:  3.15.10-bone8 
 rootfs:  debian-jessie-console-armhf-2014-08-13

 Hardware:
 BBB A5C
 Circuitco LCD4 cape
 Circuitco RS232 cape

 /home/rob/rootfs/boot/uEnv.txt

 uname_r=3.15.10-bone8
 cmdline=quiet init=/lib/systemd/systemd
 *optargs=consoleblank=0*.

 I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_
 FAQ 
 http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F
  but 
 the display is still blanking after 10  minutes.

 Would appreciate some guidance.

 Thanks
 Rob
  

  -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to the Google 
 Groups BeagleBoard group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to beagleboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] optargs in kernel 3.15.10-bone8

[Moscowbob]

Robert, I did the changes in the 
bb-kernel/KERNEL/arch/arm/boot/dts/am335x-boneblack.dts and lcd and rs232 
capes both work fine. Is there any reason I should not continue with 3.15 
kernel and revert to 3.13 ?

Thanks

Rob 

On Monday, 8 September 2014 12:34:10 UTC+1, RobertCNelson wrote:

 On Sun, Sep 7, 2014 at 7:15 PM, Moscowbob mosc...@gmail.com javascript: 
 wrote: 
  
  BBB boot from tftp and nfs - 
  kernel:  3.15.10-bone8 
  rootfs:  debian-jessie-console-armhf-2014-08-13 
  
  Hardware: 
  BBB A5C 
  Circuitco LCD4 cape 
  Circuitco RS232 cape 

 So to achieve this with a kernel (not v3.8.x) 

 http://elinux.org/Beagleboard:Capes_3.8_to_3.14 

 sudo apt-get update 
 sudo apt-get install linux-image-3.14.17-ti-r17 

 (reboot) 

 git clone -b 3.14-ti https://github.com/RobertCNelson/dtb-rebuilder.git 
 cd dtb-rebuilder/ 

 nano ./src/arm/am335x-boneblack.dts 

 Disable hdmi: 
 #include am335x-boneblack-nxp-hdmi-audio.dtsi - /* #include 
 am335x-boneblack-nxp-hdmi-audio.dtsi */ 

 Disable proto cape: 
 #include am335x-bone-basic-proto-cape.dtsi - /* #include 
 am335x-bone-basic-proto-cape.dtsi */ 

 Enable lcd 4: 
 /* #include am335x-bone-lcd4-01-00a1.dtsi */ - #include 
 am335x-bone-lcd4-01-00a1.dtsi 

 Enable uart (there's 3 options: uart1/uart2/uart4) 

 For uart 1: 
 /* #include am335x-bone-ttyO1.dtsi */ - #include 
 am335x-bone-ttyO1.dtsi 

 make 
 sudo make install 

 (reboot) 

 lcd and serial should work with a non v3.8.x capemgr kernel.. 

 (i'm hoping someone comes out with an html5 gui for the above ^^) 

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] optargs in kernel 3.15.10-bone8

[Moscowbob]

BBB boot from tftp and nfs -
kernel:  3.15.10-bone8 
rootfs:  debian-jessie-console-armhf-2014-08-13

Hardware:
BBB A5C
Circuitco LCD4 cape
Circuitco RS232 cape

/home/rob/rootfs/boot/uEnv.txt

uname_r=3.15.10-bone8
cmdline=quiet init=/lib/systemd/systemd
*optargs=consoleblank=0*.

I used this reference http://elinux.org/Beagleboard:BeagleBone_Black_FAQ 
http://elinux.org/Beagleboard:BeagleBone_Black_FAQ#Is_there_a_way_to_prevent_my_HDMI_monitor_from_sleeping_while_using_my_BBB.3F
 but 
the display is still blanking after 10  minutes.

Would appreciate some guidance.

Thanks
Rob
 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Enable LCD4 adding .dts to Kernel source v3.1x ?

[Moscowbob]

Hi All,

It works fine with Robert's 3.15 kernel. However, the lcd4 is very dim - 
how do you adjust the brightness?

Lcd also works with 3.16 and 3.17 kernels but omaplfb does not load 


Thanks
Rob


On Tuesday, 19 August 2014 21:06:22 UTC+1, Cedric Malitte wrote:

 Hi,

 Kernel changes should be in defconfig.
 I enabled a few things, but you should try with kernel config from Roberts 
 tree first.

 What I did:
 Build the kerne
 Patch 
 Rebuild 
 Sgx compile
 Rebuild
 Install


 Cédric Malitte

 Le 2014-08-19 à 15:26, stef...@gmail.com javascript: a écrit :

 Hi Cedric,

 Can you tell me what changes did you make to the kernel?

 Regards,
 Razvan

 On Tuesday, August 19, 2014 12:53:53 AM UTC+3, Cedric Malitte wrote:

 Hi,

 I added a few things to the dts and a few options to kernel

 see the files included.

 regards,

 Cedric


 2014-08-15 13:03 GMT-04:00 stef...@gmail.com:

 Hi Cedric,

 I'm trying to make a LCD4 to work with this 3.15 kernel but I have no 
 luck.
 Can you tell me what changes did you make?

 Thanks!

 Regards,
 Razvan

 -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to a topic in the 
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/beagleboard/wAcTyHqLfwg/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.


  -- 
 For more options, visit http://beagleboard.org/discuss
 --- 
 You received this message because you are subscribed to a topic in the 
 Google Groups BeagleBoard group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/beagleboard/wAcTyHqLfwg/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 beagleboard...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/d/optout.



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Circuitco LCD4 - Kernel 3.12, 3.13

[Moscowbob]

On Tuesday, 1 April 2014 14:36:27 UTC+1, RobertCNelson wrote:

 On Tue, Apr 1, 2014 at 7:02 AM, Moscowbob mosc...@gmail.com javascript: 
 wrote: 
  First of all, thank you to all who share their knowledge and experience, 
  without you guys us newbies will have a hard time learning. 
  
  I have been playing around with various kernels and just in general 
 getting 
  familiar with Linux and the BBB in general. I managed to build QT 4.8.5 
 with 
  RCN 3.8.13-Bone41 and all seems well. Now I wish to use QT with SGX and 
 as I 
  understand Robert has provided scripts to build all the required drivers 
 etc 
  but the later kernels do no support Cape manager and overlays so the lcd 
 is 
  not enabled. 

 SGX was back-ported to the 3.8 tree as of the bone41 release. 

  
  Would somebody please explain how to enable the LCD4 from Circuitco in 
 the 
  new kernels(if that is currently possible). 

 Regards, 

 -- 
 Robert Nelson 
 http://www.rcn-ee.com/ 


Thank you Robert  I am aware of the patches as you mention however, I am 
unsure how to actually build the graphics sdk in question with using your 
kernel 3.8.13-bone41(43.1). The information I have found is using different 
build systems and are not clear, whereas your later kernels have all this 
integrated but do not support the LCD4 cape.

Can your script in the later kernels be used to build the drivers for the 
3.8 kernel ?

Thanks. 

 

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Circuitco LCD4 - Kernel 3.12, 3.13

[Moscowbob]

First of all, thank you to all who share their knowledge and experience, 
without you guys us newbies will have a hard time learning.

I have been playing around with various kernels and just in general getting 
familiar with Linux and the BBB in general. I managed to build QT 4.8.5 
with RCN 3.8.13-Bone41 and all seems well. Now I wish to use QT with SGX 
and as I understand Robert has provided scripts to build all the required 
drivers etc but the later kernels do no support Cape manager and overlays 
so the lcd is not enabled.

Would somebody please explain how to enable the LCD4 from Circuitco in the 
new kernels(if that is currently possible).

Thank you.



-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.