On 23/05/2016 22:37, Gedare Bloom wrote:
How does this affect user applications?
It should not but if a user has an application that is using the plugin
interface there is a struct name change. The previous struct ended in
'_t' and that is reserved for POSIX plus the name included _printk_ an
On 23/05/2016 23:19, Isaac Gutekunst wrote:
Hi Vivek,
This is looking good!
I agree.
I somewhat sketchy solution for getting binary files off a target is to
print them as intel hex, and copy them from the terminal. If the Zynq
bsp supports networking, you could setup a TFTP server. My ugly t
Am Sonntag, 22. Mai 2016 23:26:07 UTC+2 schrieb bel:
>
>
>
> On Sunday, May 22, 2016 at 11:04:44 AM UTC+2, Christian Mauderer wrote:
>>
>>
>> I created a draft for a callback. It's not worked out and only thought as
>> a basis for further discussions:
>>
>>
>> https://github.com/c-mauderer/ci
How does this affect user applications?
On Mon, May 23, 2016 at 2:55 AM, Chris Johns wrote:
> This change adds rtems_printf and related functions and wraps the
> RTEMS print plugin support into a user API. All references to the
> plugin are removed and replaced with the rtems_printer interface.
>
Hi Vivek,
This is looking good!
I somewhat sketchy solution for getting binary files off a target is to print
them as intel hex, and copy them from the terminal. If the Zynq bsp supports
networking, you could setup a TFTP server. My ugly trace implementation
implements the lttng-live protocol
