Issues with DALimit

Steve, could you please explain what on Earth you are talking about?

@Tennant: You are using v5.19 ROM, which is a development version, which was available from ROOL.
v5.21 ROM is also a development version, available from ROOL, and the one available for download now should contain the fix.

Does that help?

Thanks for your polite reply, Martin.

I didn’t know that these ROMs could be downloaded.

Is it the OMAP4 thing?

That’s great Jeffrey, but what good does it do me?

Another bug quashed, that’s a good thing, right?

Is it the OMAP4 thing?

Dunno – it depends on what hardware you are running on, and you have not said. Use the Downloads button above and click the icon for your machine. Some have a stable v5.20 ROM available, others only a v5.21 development ROM. You will need the development one to include Jeffreys fix above.

In the absence of an ‘official’ ROOL release. It is difficult to know when to recommend users use a development build. Now is a good illustration. Jeffreys bug quash I was starting to think seemed a good time, but then Malcolm Hussain-Gambles has reported that it slows some programs significantly. Watch this space!

As Martin has pointed out, the 5.19 that Tennant is using is very outdated, I’m afraid. It is important not to think of the “ROM” as a fixed item like it was in the RiscPC – in modern machines, it is a piece of software like any other, and can easily be updated. Indeed, R-Comp Interactive customers have been using solid 5.21 versions for 18+ months I think.

Part of our PandaLand Support Scheme, and our machines as a whole, is regular, tested upgrades with our simple “one click” update mechanism, that upgrades not only the OS, but any necessary connected files (eg. necessary !boot updates, or default cmos etc). This simple “roll-on, roll-off” style of upgrade is designed to make updating machines very straightforward, but there’s no reason you can’t simply download ROMs from the ROOL site and “DIY”.

The big difference, as Chris has suggested, is knowing when to “jump”. That’s why we test a lot and only make formal releases when we’re happy. The next “official” ROOL build will be 5.22 in due course, which I also do testing/QA for.

It’s worth pointing out that the recent discoveries of cache issues (etc etc) on Panda stem directly from the work we’re doing on the i.MX6 project. We’re doing intense testing and feedback and fixing at the moment (seriously, it’s late nights, every day of the week) feeding back seemingly endless traces and information to ensure that remaining bugs can be tracked and found. I know some may be wondering what benefit the i.MX6 project has for non-R-Comp customers, but hopefully examples like this make it abundantly clear. Indeed, this process has been on-going for a long, long time.

That said, if it wasn’t for the tireless work of Jeffrey, John, Willi and everyone else, then none of this would come to pass. Not to mention all at ROOL, and so on…