Re: [armv7] introducing tipru(4)

I am pretty unhappy about drivers like this arriving in the tree. I just don't see any trustworthy way to use them, and lacking trust -- I don't understand the worth. Givings hugs to trustworthy designs is an OpenBSD agenda. Giving scowls to untrustworthy designs is another OpenBSD agenda.

Re: [armv7] introducing tipru(4)

On Wed, Jul 6, 2016 at 5:41 AM, Damien Miller wrote: > That sounds like a reasonable compromise - it would let the admin load > code to the PRUs in rc.securelevel for later use, or set > kern.securelevel=0 in sysctl.conf if they wanted to do development > on a multi-user

Re: [armv7] introducing tipru(4)

On Wed, 6 Jul 2016, Ian Sutton wrote: > * tipru comes disabled by default. Attempts to enable tipru, and > following modification of the instruction/data/shared memory > spaces, are only allowed when the system's securelevel(7) is equal > or lesser than zero. When the system's

Re: [armv7] introducing tipru(4)

I have revised tipru(4) according to advice given in this thread: On Mon, Jul 4, 2016 at 10:30 PM, Jonathan Gray wrote: > There aren't any suser checks either. On Tue, Jul 5, 2016 at 12:56 AM, Jonathan Gray wrote: > Perhaps it could only permit access at a

Re: [armv7] introducing tipru(4)

On Tue, Jul 5, 2016 at 12:56 AM, Jonathan Gray wrote: > I don't have time to look into how tied to the rest of the > system the pru is at the moment. I can save you the trouble; page 198 of am335x TRM: "The PRUs have access to all resources on the SoC through the Interface/OCP

Re: [armv7] introducing tipru(4)

On Tue, Jul 05, 2016 at 01:39:18AM -0400, Ian Sutton wrote: > On Mon, Jul 4, 2016 at 10:30 PM, Jonathan Gray wrote: > > Lack of fdt use aside, we don't want to enable something that > > allows userspace access to system memory like this. > > I can understand this sentiment. Maybe

Re: [armv7] introducing tipru(4)

On Mon, Jul 4, 2016 at 10:30 PM, Jonathan Gray wrote: > Lack of fdt use aside, we don't want to enable something that > allows userspace access to system memory like this. I can understand this sentiment. Maybe next time.. Are you saying you are catagorically opposed to a PRU

[armv7] introducing tipru(4)

I have written some software to support the PRU (Programmable Realtime Unit) integrated in Texas Instrument's line of ARM SoCs, specifically the am335x chips. The PRU is a 32-bit realtime processor that exists as a subsystem on the SoC. You can read more about it in the linked man pages. Included