Am 27.07.2013 21:37, schrieb Stefan Weil: > Am 27.07.2013 19:43, schrieb Peter Maydell: >> On 27 July 2013 17:18, Hervé Poussineau <hpous...@reactos.org> wrote: >>> Another solution would be to add a big dummy memory regions on all MIPS >>> boards >>> to catch memory accesses and not raise an exception. However, this means >>> that >>> each MIPS board will have its own unassigned memory handler, different from >>> the >>> global QEMU one. >> Better would be to at least provide fake RAZ/WI implementations of >> devices for the boards, rather than making the dummy region cover >> the whole of the address space. Not 1.6 material, though. > > I prefer keeping the correct code for target-mips/op_helper.c > and adding either the big dummy memory regions or fake > device implementations (both with TODO comments) for 1.6.
The problem I see with that is, so far no one has stepped up with a list of what memory ranges / devices we are talking about. The simplest for 1.6 might be to re-add an #ifndef TARGET_MIPS around the refactored call to restore old behavior. Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
