On 5 August 2013 15:07, Aurélien Jarno <aurel...@aurel32.net> wrote: > On Mon, Aug 05, 2013 at 03:53:08PM +0200, Hervé Poussineau wrote: >> Another idea (not tested): override the >> CPUClass->do_unassigned_level on board level, to only raise IBE and >> no DBE.
This sounds like a bit of a layering violation... >> That way, right behaviour is kept in global code, and "bad" code is >> only at board level, where it can be removed later board after >> board. > > The problem is that it looks like the code is not "bad". It seems that > real hardware just ignore such accesses, so this should stay forever. But this is just board level behaviour, right? So the right place to implement it is definitely in the board model. If this is how the board works I think my first try would be to have the board register a background region covering the whole system memory space which returns 0 or -1 or whatever the board does. -- PMM
