Detlef Vollmann wrote:
Hello,
the x86 branch supports kernel 2.6.19, but the ARM branch only supports
2.6.15. Is there a specific reason for this?
Does anybody have a feeling what would be needed to be changed
for 2.6.19 support?
I guess the reason is that it is some work that needs to be
Gilles Chanteperdrix wrote:
Detlef Vollmann wrote:
Hello,
the x86 branch supports kernel 2.6.19, but the ARM branch only supports
2.6.15. Is there a specific reason for this?
Does anybody have a feeling what would be needed to be changed
for 2.6.19 support?
I guess the reason is
Gilles Chanteperdrix wrote:
I guess the reason is that it is some work that needs to be done. I had
ported from 2.6.15 to 2.6.17,
Interesting.
Is that patch available somewhere?
it was a trivial task as far as I could
see, but never tried to port to 2.6.19. There were some architectural
Hi Philippe,
likely a regression of latest timer base patches: with periodic support
enabled (haven't tested the off case yet), latency -t1/2 no longer work.
I have no time to look at this, so I just dump my report here. :)
Jan
PS: Is there an official nucleus API to convert dates between
On Thu, 2007-01-04 at 15:52 +0100, Jan Kiszka wrote:
Hi Philippe,
likely a regression of latest timer base patches: with periodic support
enabled (haven't tested the off case yet), latency -t1/2 no longer work.
I have no time to look at this, so I just dump my report here. :)
Jan
PS:
On Thu, 2007-01-04 at 15:52 +0100, Jan Kiszka wrote:
Hi Philippe,
likely a regression of latest timer base patches: with periodic support
enabled (haven't tested the off case yet), latency -t1/2 no longer work.
I have no time to look at this, so I just dump my report here. :)
Btw, it
On Thu, 2007-01-04 at 16:16 +0100, Philippe Gerum wrote:
On Thu, 2007-01-04 at 15:52 +0100, Jan Kiszka wrote:
Hi Philippe,
likely a regression of latest timer base patches: with periodic support
enabled (haven't tested the off case yet), latency -t1/2 no longer work.
I have no time to
