On Donnerstag, 28. Juni 2018 11:32:08 CEST Peter Maydell wrote:
Thanks for your quick answer.
> I'm not sure your bisection has landed on the right thing, as > d9f8bbd8eb4e95 should be a no-behaviour-change commit.
Yes, i saw that already. But strangely, the commit before worked (tested manually after the bisect), and with that commit i get the division by zero.
The problem is that the kernel stops booting at this point (maybe not because of the exception, but that is the last message printed)
>Unfortunately the cprman hardware is as far as I can >determine undocumented
Would there be some way to fake it at least, so that linux does not get a zero baudrate?
On Donnerstag, 28. Juni 2018 11:32:08 CEST Peter Maydell wrote:
Thanks for your quick answer.
> I'm not sure your bisection has landed on the right thing, as
> d9f8bbd8eb4e95 should be a no-behaviour-change commit.
Yes, i saw that already. But strangely, the commit before worked (tested
manually after the bisect), and with that commit i get the division by zero.
The problem is that the kernel stops booting at this point (maybe not because
of the exception, but that is the last message printed)
>Unfortunately the cprman hardware is as far as I can
>determine undocumented
Would there be some way to fake it at least, so that linux does not get a zero
baudrate?