Re: BigRamPlus arrived

2013-12-12 Thread Michael Schmitz
Geert, Might be cleanest - please bump the bootinfo version in that case so we can fall back to some default logic if the device tree is absent. Oops, I forgot to insert the obligatory smiley. Do tell ... I was briefly wondering about that. Weirder things have happened. I don't think

Re: BigRamPlus arrived

2013-12-11 Thread Geert Uytterhoeven
On Wed, Dec 11, 2013 at 7:41 AM, Michael Schmitz wrote: >> On Tue, Dec 10, 2013 at 10:07 AM, Thorsten Glaser wrote: Why not? Those address ranges are defined in the offical Amiga Hardware Reference Manual and are standardized for Amiga. For other subarchs this is >>> >>>

Re: BigRamPlus arrived

2013-12-10 Thread Michael Schmitz
Geert, On Tue, Dec 10, 2013 at 10:07 AM, Thorsten Glaser wrote: Why not? Those address ranges are defined in the offical Amiga Hardware Reference Manual and are standardized for Amiga. For other subarchs this is ^^ a tota

Re: BigRamPlus arrived

2013-12-10 Thread Thorsten Glaser
Geert Uytterhoeven dixit: >Do you want m68k to move to device trees? Uhm… you’re the Linux kernel developer, not me… I’m just cautious ☺ Groeten, //mirabilos -- This space for rent. -- To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Conta

Re: BigRamPlus arrived

2013-12-10 Thread Geert Uytterhoeven
On Tue, Dec 10, 2013 at 10:07 AM, Thorsten Glaser wrote: >>Why not? Those address ranges are defined in the offical Amiga Hardware >>Reference Manual and are standardized for Amiga. For other subarchs this is >^^ >>a totally diff

Re: BigRamPlus arrived

2013-12-10 Thread Thorsten Glaser
Ingo Jürgensmann dixit: >Why not? Those address ranges are defined in the offical Amiga Hardware >Reference Manual and are standardized for Amiga. For other subarchs this is ^^ >a totally different matter, of course. And maybe s

Re: BigRamPlus arrived

2013-12-10 Thread Ingo Jürgensmann
On Mon, Dec 09, 2013 at 08:54:23PM +, Thorsten Glaser wrote: > Ingo Jürgensmann dixit: > >Or even easier: we know that memory on accelerator cards will be > >located at 0x0800 (didn't count the zeros ;) and should have the > Oh, please not… Why not? Those address ranges are defined in the

Re: BigRamPlus arrived

2013-12-09 Thread Thorsten Glaser
Ingo Jürgensmann dixit: >Or even easier: we know that memory on accelerator cards will be >located at 0x0800 (didn't count the zeros ;) and should have the Oh, please not… Geert Uytterhoeven dixit: >On Sun, Dec 8, 2013 at 10:58 PM, Michael Schmitz >> It already is (has to be, due to lack

Re: BigRamPlus arrived

2013-12-09 Thread Geert Uytterhoeven
On Sun, Dec 8, 2013 at 10:58 PM, Michael Schmitz wrote: >> Amiboot already has memfile support, so you can specify the order of the >> memory chunks. What's "missing" is a way to specify memory chunk >> priorities. >> A naive method is to just assume the first chunk has the highest priority >> (bu

Re: BigRamPlus arrived

2013-12-08 Thread Michael Schmitz
Geert, On Sun, Dec 8, 2013 at 1:17 PM, Ingo Jürgensmann wrote: This means that the kernel would be located in the slow ZorroIII memory (256M), which should be avoided in the long run. We need support for SPARSEMEM and priority of mem chunks as in AmigaOS, i.e. memory chunk with highest p

Re: BigRamPlus arrived

2013-12-08 Thread Ingo Jürgensmann
Am 08.12.2013 um 14:12 schrieb Geert Uytterhoeven : >> - find out if we need a new amiboot > I'd really like to avoid the need for a new amiboot. Yeah,me too... ;) > You would only need a new amiboot when extending the passed bootinfo. > > Amiboot already has memfile support, so you can specify

Re: BigRamPlus arrived

2013-12-08 Thread Geert Uytterhoeven
On Sun, Dec 8, 2013 at 1:17 PM, Ingo Jürgensmann wrote: > This means that the kernel would be located in the slow ZorroIII memory > (256M), which should be avoided in the long run. We need support for > SPARSEMEM and priority of mem chunks as in AmigaOS, i.e. memory chunk with > highest priori

Re: BigRamPlus arrived

2013-12-08 Thread John Paul Adrian Glaubitz
On 12/08/2013 02:00 PM, Geert Uytterhoeven wrote: > What's the last version you have? I have a few more local changes that > I haven't released so far. The current one from Debian. I haven't found the time yet to re-install my Mac Mini G4 with Debian so I have a PowerPC build host (zorroutils is a

Re: BigRamPlus arrived

2013-12-08 Thread Geert Uytterhoeven
Hi Adrian, On Sun, Dec 8, 2013 at 1:21 PM, John Paul Adrian Glaubitz wrote: > On 12/08/2013 01:17 PM, Ingo Jürgensmann wrote: >> spice:/home/ij# lszorro >> 00: MacroSystems USA Warp Engine 40xx [Accelerator, SCSI Host Adapter and >> RAM Expansion] >> 01: Unknown device 0e3b:20:00 > > Just a shor

Re: BigRamPlus arrived

2013-12-08 Thread John Paul Adrian Glaubitz
On 12/08/2013 01:17 PM, Ingo Jürgensmann wrote: > spice:/home/ij# lszorro > > 00: MacroSystems USA Warp Engine 40xx [Accelerator, SCSI Host Adapter and RAM > Expansion] > 01: Unknown device 0e3b:2

BigRamPlus arrived

2013-12-08 Thread Ingo Jürgensmann
Hi! These days the ordered BigRamPlus memory expansion cards arrived that were sponsored by the Debian project. Adrian took one of those cards for Elgar and sent the other four cards to me. I'll take 3 of them for Arrakis, Spice and Vivaldi and send the fourth to Christian for Kullervo. The g