Hi
I refactored the whole buildbot quite a lot. The following changes are worth
mentioning and were applied last saturday morning:
- upgraded to buildbot 0.7.4 (required to for better warning/logs)
- to speed up builds during the day reorganised the buildbot to
- quick builds which only calls
Wolfgang Grandegger wrote:
> Hello,
>
> attached is a patch changing:
>
>* ksrc/drivers/can/rtcan_dev.c (rtcan_dev_register): Bug fixed
>when maximum number of devices is exeeded.
Applied.
>
> BTW, a similar bug is present in RTnet as well.
Yep, fixed there as well. Thanks.
All pendi
Here is the second maintenance release for the v2.2.x branch. Short
log follows:
[nucleus]
* Fix PI chain walk.
* Fix priority update for threads sleeping on a resource by
priority without undergoing PI.
* Fix potential FPU corruption in rare thread initia
Hello,
attached is a patch changing:
* ksrc/drivers/can/rtcan_dev.c (rtcan_dev_register): Bug fixed
when maximum number of devices is exeeded.
BTW, a similar bug is present in RTnet as well.
Wolfgang.
+ diff -u xenomai/ChangeLog-ENOMEM xenomai/ChangeLog
--- xenomai/ChangeLog-ENOMEM 2006-
Hi Jan,
Jan Kiszka wrote:
For review:
This patch folds the rt-threads of rtcanrecv/send into the main thread,
assigns unique thread names, and lowers the priorities to some less
critical level. Furthermore, rtcanrecv is enhanced by a printout of the
CAN device and support for listening on all i
Hi Jan,
Jan Kiszka wrote:
For review:
Here comes a tiny but fairly useful new CAN driver: a virtual CAN bus
consisting of 2..n devices (see module parameter). Transmission takes
places from the sender to all other devices on the bus, just like in
real life.
This driver was already helpful for