On Mon, Aug 24, 2015 at 1:50 PM, Pavel Pisa wrote:
> Hello Giao, Joel and Gedare,
>
> there are more technical problems to discuss.
> But I start with question if RPi video support
> should be unconditional. I am not sure if VideoCore
> activation has some consequences to ARM system throughput
> b
Hello Gedare,
On Friday 21 of August 2015 16:46:41 Gedare Bloom wrote:
> I believe CANFestival comes from Pavel Pisa's group. He is active with
> RTEMS and interested in pushing forward CAN improvements, but time is
> always a problem. He's on vacation but may get to this thread after he
> gets ba
Hello Giao, Joel and Gedare,
there are more technical problems to discuss.
But I start with question if RPi video support
should be unconditional. I am not sure if VideoCore
activation has some consequences to ARM system throughput
but at least it slows down startup.
So there can be resons to dis
We should consider how to continue making improvements in this area of RTEMS.
On Mon, Aug 24, 2015 at 1:25 PM, Rohini Kulkarni wrote:
> OK, thanks all for the views. That gave plenty insight into the details I
> had not thought of earlier. Clearly not the way to go.
>
> But then is such refactori
OK, thanks all for the views. That gave plenty insight into the details I
had not thought of earlier. Clearly not the way to go.
But then is such refactoring a good idea? These changes even if modified
will apply only to cp15 ARM BSPs.
On 24 Aug 2015 21:20, "Pavel Pisa" wrote:
> Hello Chris and
Hello Chris and Rohini,
I have returned and catching the emails flow.
But please, consider that for some architectures it is critical
to have MMU table runtime alterable.
I.e. on RPi the actual memory division to cacheable
and peripheral area is know only at runtime. It depends
on user provided
Ok I experimented on and this is what I found out:
This is what I'm doing:
App:
fd = open(RTEMS_SYSFLASH_DEVICE_NAME, O_RDWR);
printk("Errno: (%d:%s).", errno, strerror(errno));
assert(0);
Driver:
rtems_device_driver rtems_sysflash_open(rtems_device_major_number major,
rtems_device
Hi Chris,
I am pretty sure the driver is working fine yes. I had this issue for some time
and ignored the error messages during development as I always get a negative
value. Now the driver is working is as it should and I am enforcing the error
to test this.
Regards,
Indy
_
