No.... A Q60 has a 68060 CPU, the correct shorthand would be: Q60-clock_speed, e.g Q60-66 or in your case a Q60-80 with a 80Mhz clock speed.pjw wrote:Shorthand for Q60 @ 80 MHzDerek_Stewart wrote:<>
Whats a Q80?
you have just implied a 68080 CPU
No.... A Q60 has a 68060 CPU, the correct shorthand would be: Q60-clock_speed, e.g Q60-66 or in your case a Q60-80 with a 80Mhz clock speed.pjw wrote:Shorthand for Q60 @ 80 MHzDerek_Stewart wrote:<>
Whats a Q80?
I have a quick look at the C source code, but could see were to change the ram size, but judging the previous comments, the change is not straight forward and beyond my programming skills.XorA wrote:It occurs to me when I make this change software that uses the top 8 bits of the A? registers for flags will start to fail. I am assuming that case is actually quite rare in QDOS?XorA wrote:You need to change the code where allocation occurs.Derek_Stewart wrote: Hi,
I can only allocate maximum of 16Mb in sQLux and UQLX, how do I increase the memory size?
Given everyone (https://github.com/janbredenbeek/Minerva4Q68) keeps saying 16M is the largets Minerva can address, I wonder why you want this change?Derek_Stewart wrote:I have a quick look at the C source code, but could see were to change the ram size, but judging the previous comments, the change is not straight forward and beyond my programming skills.XorA wrote:It occurs to me when I make this change software that uses the top 8 bits of the A? registers for flags will start to fail. I am assuming that case is actually quite rare in QDOS?XorA wrote:
You need to change the code where allocation occurs.
Sorry, I did not suggest the change, or even use SMSQ/E.XorA wrote:Given everyone (https://github.com/janbredenbeek/Minerva4Q68) keeps saying 16M is the largets Minerva can address, I wonder why you want this change?Derek_Stewart wrote:I have a quick look at the C source code, but could see were to change the ram size, but judging the previous comments, the change is not straight forward and beyond my programming skills.XorA wrote:
It occurs to me when I make this change software that uses the top 8 bits of the A? registers for flags will start to fail. I am assuming that case is actually quite rare in QDOS?
Code: Select all
k.issp equ $4c024c02 initial ssp - no longer used as such
l vec.l k.issp ss_ramt ; 00 0 initial SSP 08 2 initial PC
Maybe I don't understand your conclusion, but this initial A7 is never referenced. It's changed early in the reset routine to a real value, so this is no show stopper.XorA wrote:So this means Minerva requires that addresses are truncated, otherwise SSP is a way out in the wilds and gets carried through the whole ROM on uqlx codebase!Code: Select all
k.issp equ $4c024c02 initial ssp - no longer used as such l vec.l k.issp ss_ramt ; 00 0 initial SSP 08 2 initial PC
it definitely is referenced. if i remove address truncation i need to zero first byte of rom to boot. I can see this address leaking into addresses later in boot.mk79 wrote:Maybe I don't understand your conclusion, but this initial A7 is never referenced. It's changed early in the reset routine to a real value, so this is no show stopper.XorA wrote:So this means Minerva requires that addresses are truncated, otherwise SSP is a way out in the wilds and gets carried through the whole ROM on uqlx codebase!Code: Select all
k.issp equ $4c024c02 initial ssp - no longer used as such l vec.l k.issp ss_ramt ; 00 0 initial SSP 08 2 initial PC
i have not yet tracked down where, and may obviously be some uqlx hack gone wrong.XorA wrote:it definitely is referenced. if i remove address truncation i need to zero first byte of rom to boot. I can see this address leaking into addresses later in boot.mk79 wrote:Maybe I don't understand your conclusion, but this initial A7 is never referenced. It's changed early in the reset routine to a real value, so this is no show stopper.XorA wrote:So this means Minerva requires that addresses are truncated, otherwise SSP is a way out in the wilds and gets carried through the whole ROM on uqlx codebase!Code: Select all
k.issp equ $4c024c02 initial ssp - no longer used as such l vec.l k.issp ss_ramt ; 00 0 initial SSP 08 2 initial PC
That's what I suspect. After reset it just executes ii_raw, which doesn't use the stack at all (or any RAM really), and immediately afterwards at the label "retry" it is set to a sensible value.XorA wrote:i have not yet tracked down where, and may obviously be some uqlx hack gone wrong.