| norly | Chain|Q, correct, you can't map the 256 MB RAM on the ZZ9000, but i also never claimed that. i guess we've been talking about different things :) | 00:14 |
|---|---|---|
| _Bnu | Z2 has everything to do with the fact. | 02:31 |
| _Bnu | You cannot address 32-bit ranges over a Z2 expansion. | 02:32 |
| _Bnu | You CAN address 32-bit ranges if you're something like the BigRAM2630 which is on the CPU bus. | 02:32 |
| _Bnu | Oh, I misread. | 02:32 |
| _Bnu | Anyway, you do it in the boot ROM of the device, it is really that easy. | 02:33 |
| _Bnu | You know where you can address your RAM and what size it is, you just set up a call to AddMemList call in the boot ROM and map it there. | 02:34 |
| _Bnu | https://github.com/beeanyew/pistorm/blob/wip-crap/platforms/amiga/piscsi/device_driver_amiga/bootrom.s#L265-L281 | 02:34 |
| _Bnu | I just check if there's any RAM at $10000000, and if there is it's most likely the 128MB of Z3 Fast configured in default.cfg. | 02:35 |
| _Bnu | So I just add it there, and then it's available to AmigaOS on boot to WB. | 02:35 |
| _Bnu | I was just lamenting that it couldn't be used on the ZZ9000, due to Zorro II, haha. | 02:35 |
| _Bnu | But if the ZZ9000 could have a direct connection to something like the a PiStorm or a 32-bit CPU board... then you could do it. | 02:45 |
| _Bnu | But as for your question about avoiding changing something in the Kickstart ROM, no you can not, without a boot ROM, because none of the A500/A2000 Kickstarts attempt to map any Fast RAM except for Z2 Fast. | 02:46 |
| norly | _Bnu, i'm confused. why change the kickrom, if you can simply manually add the RAM from within bootrom code? | 02:49 |
| norly | i.e. have the RAM physically available, and then emulate a Z2 device as a carrier for an autoconfig ROM? | 02:50 |
| norly | i guess that's what you're doing and what everyone else is doing, right? | 02:50 |
| _Bnu | You were the one who asked if it could be done without changing the Kickstart ROM. | 02:50 |
| _Bnu | And I assumed you meant automatically. | 02:51 |
| _Bnu | Also, no, this is not what everyone is doing as far as I know. | 02:53 |
| _Bnu | I don't believe any of the TerribleFire boards can actually add "Z3 Fast" to Kickstart 1.3? | 02:54 |
| norly | oh, i'm confused | 02:54 |
| _Bnu | The TF boards simply provide a "Zorro III Fast RAM" PIC. | 02:55 |
| norly | as far as i know, the CPU boards all have RAM mapped into the CPU board area, not into Z3 area | 02:55 |
| _Bnu | Which can configure automatically in Kickstart 2.0 and up. | 02:55 |
| _Bnu | No, you would have to check ShowConfig to see if that's the case. | 02:55 |
| norly | hrm, i guess i should | 02:56 |
| norly | BigRAM2630: RAM:Node type $A, Attributes $505 (FAST), at $1000000-$7FFFFFF (112.0 meg) | 02:56 |
| norly | that's most definitely not autodetected by kickstart, so what they do is to inject a fake Z2 card bootrom, and the code there then AddMems this 112M range | 02:57 |
| norly | and this is definitely not in Z3 range | 02:58 |
| _Bnu | Yes, that is indeed the CPU local fast address range. | 02:58 |
| norly | so yeah, this is not autodetected by kickstart itself, but it also does not require a kickstart modification | 02:58 |
| _Bnu | It would, if the boot ROM didn't handle it. | 02:58 |
| norly | oh? kickstart probes for memory there? | 02:59 |
| _Bnu | Some Kickstarts do, yes. | 02:59 |
| norly | interesting | 02:59 |
| _Bnu | Which is why I'm saying it would require modification. | 02:59 |
| norly | okay, i'm lost again. if kickstart adds your memory automatically, then why modify it? | 03:00 |
| _Bnu | You would need to use an A1200, A3000 or A4000 Kickstart, or modifications imported from those. A3000 and A4000 would be completely unsuitable for it. | 03:00 |
| _Bnu | What. | 03:00 |
| _Bnu | I already told you. | 03:00 |
| _Bnu | The A500/A2000 Kickstarts do not attempt to map this automatically. | 03:00 |
| norly | ah ok | 03:00 |
| norly | got it | 03:00 |
| norly | in that case, isn't a fake zorro ROM an easier solution, because it works on all kickstarts? | 03:01 |
| _Bnu | Sure, on a Z3 machine. | 03:01 |
| _Bnu | Otherwise you need to be on the CPU board. | 03:01 |
| norly | are we talking about memory on PiStorm, or on ZZ9000? | 03:02 |
| _Bnu | ZZ9000. | 03:02 |
| norly | ok, that's where we were talking about different things | 03:02 |
| _Bnu | Why would you be talking about the PiStorm when I'm trying to explain why it doesn't work on a physical Z2 board. ('A`) | 03:03 |
| _Bnu | The PiStorm is the CPU, it can do whatever* it wants. | 03:03 |
| norly | exactly | 03:03 |
| norly | that's what got me confused | 03:03 |
| norly | there's no way to map 128M from ZZ9000 on Z2, so why would you hack the kickrom for that? hence my assumption that you were talking about pistorm | 03:04 |
| norly | anyway, let's call it off, enough confusion for now. thanks for your patience :) | 03:05 |
| _Bnu | I'm saying there's no way to have it map any range other than Z2 automatically on Kickstart 1.3, becasue it does not do anything other than that. | 03:07 |
| _Bnu | You can not use a fake Z3 autoconf ROM (like on the TF cards I saw) on Kickstart 1.3, because Kickstart 1.3 does not configure Z3 devices in Z2 autoconf space. | 03:08 |
| _Bnu | So you would have to make your own boot ROM and AddMemList it in that, which as far as I know it does not. | 03:08 |
| _Bnu | There's no perfect solution, which is why I added the hack to the PiSCSI boot ROM for 1.3 specifically. | 03:09 |
| + js[m] (~jsnilim@2001:470:69fc:105::232) | 11:29 | |
| js[m] | Nice. There is a matrix bridge now. So I can join again :) | 11:30 |
| + Coolhandluke (~Coolhandl@79.138.204.25.bredband.tre.se) | 12:20 | |
| norly | js[m], thanks for letting us know, i'll spread the word elsewhere :) | 15:01 |
| - Coolhandluke (QUIT: Ping timeout: 248 seconds) (~Coolhandl@79.138.204.25.bredband.tre.se) | 15:38 | |
| + Coolhandluke (~Coolhandl@79.138.204.25.bredband.tre.se) | 15:53 | |
| - shanshe_ (QUIT: Quit: ZNC 1.7.5 - https://znc.in) (~shanshe@246.red-83-59-108.dynamicip.rima-tde.net) | 16:04 | |
| + shanshe (~shanshe@246.red-83-59-108.dynamicip.rima-tde.net) | 16:38 | |
| * js[m] -> js- | 17:27 | |
| * js- -> js[m] | 17:31 | |
| - js[m] (QUIT: Quit: node-irc says goodbye) (~jsnilim@2001:470:69fc:105::232) | 17:32 | |
| + js[m] (~js@2001:470:69fc:105::232) | 17:32 | |
| - js[m] (QUIT: Client Quit) (~js@2001:470:69fc:105::232) | 17:33 | |
| + js[m] (~js@2001:470:69fc:105::232) | 17:33 | |
| - js[m] (QUIT: Client Quit) (~js@2001:470:69fc:105::232) | 17:33 | |
| + js[m] (~js@2001:470:69fc:105::232) | 17:34 | |
| - Coolhandluke (QUIT: Quit: Client exiting) (~Coolhandl@79.138.204.25.bredband.tre.se) | 18:49 | |
| + Coolhandluke (~Coolhandl@79.138.204.25.bredband.tre.se) | 18:55 | |
| + xenial-user (~puppy@213.237.94.134) | 19:15 | |
| - xenial-user (QUIT: Quit: Leaving) (~puppy@213.237.94.134) | 20:54 | |
| + xenial-user (~puppy@213.237.94.134) | 20:54 | |
| * xenial-user -> Crabster | 21:34 | |
| - Coolhandluke (QUIT: Quit: Client exiting) (~Coolhandl@79.138.204.25.bredband.tre.se) | 23:38 | |
| - js[m] (QUIT: Quit: node-irc says goodbye) (~js@2001:470:69fc:105::232) | 23:56 | |
| + js[m] (~js@2001:470:69fc:105::232) | 23:57 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!