Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
Yes. This is for disassembling and analyzing a game ROM set. Right now I was just loading it in the MAME debugger, eyeballing the address map from the driver code, dumping the relevant ranges, and passing them to the disassembler with manually specified base addresses.
That sounds like your best bet, that or writing a Lua or Python script to analyze the code for a specific driver. Any general-purpose solution would be rife with exceptions.
For example, the sun4 driver: The main address map simply maps in a single handler across the entire address space which bounces all CPU accesses through an MMU handler, then the *actual* hardware handlers are mapped into an address_map_bank_device.
Sure, I wasn't expecting a general solution. And even for simpler cases, bank switching throws a wrench in things if you try to represent things to the disassembler with a flat address map. I was just hoping to automate the simple, mechanical task I was already doing.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
