Hi John! Yes, you're right. The task is to load or reload firmware to the PRUSS and run it, controlled by host software executing under user privilegues. Prussdrv fulfills this task, the other doesn't. So I compared apples and oranges. Apples and oranges shouldn't go into the same am335x_pru_package. Thanks for your indorsement.
All that features (you forget to mention debugging) are not really made for main stream users. And who cares about that features when the solution doesn't provide the basics (and is slow and memory consuming and not really easy to handle and is limited to a special compiler and ...)? I wonder how such an experimental peace of software can find its way to any linux image and all users have to work around it, in order to make their system usable. Even if it'll be working and will be useful some times in future, this is stuff for an external package in the depths of the development section, and shouldn't pollute any image by default. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/cd2c68d6-8cd6-415d-bccc-c907971b7660%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
