|To:||Ralf Baechle <email@example.com>|
|Subject:||Re: O2 RM7000 Issues|
|From:||Sergey Rogozhkin <firstname.lastname@example.org>|
|Date:||Tue, 17 Jul 2007 13:04:00 +0400|
|Cc:||Linux MIPS List <email@example.com>, "Gleb O. Raiko" <firstname.lastname@example.org>, Kumba <email@example.com>|
|References:||<4687DCE2.firstname.lastname@example.org> <468825BE.email@example.com> <firstname.lastname@example.org> <20070704152729.GA2925@linux-mips.org> <20070704192208.GA7873@linux-mips.org>|
|User-agent:||Thunderbird 184.108.40.206 (X11/20070102)|
Big loud bell began ringing. The RM7000 fetches and decodes multiple instructions in one go. And just like the E9000 cores it does throw an exception if it doesn't like one of the opcodes even if that doesn't actually get executed. The kernel has a workaround for this PMC-Sierra peculiarity (I call it a bug) but it's only being activated for E9000 platforms.
Are you really sure RM7000 has this bug? Workaround mentioned above breaks gcc signal frame unwinding mechanism: it search for sigcontext struct at fixed offset from signal trampoline.
And one another known RM7000 bug, maybe not taken into account by linux: errata 38. r4k_wait is not suitable for RM7000 on some systems. I don't know if "O2" is affected.
|<Prev in Thread]||Current Thread||[Next in Thread>|