Hi Geert,
The problem is - it dies when calling ioremap:
stram_virt_offset = ioremap(stram_pool.start,
resource_size(&stram_pool) -
stram_pool.start);
Why do you subtract stram_pool.start from the size again?
Good question - no idea wh
Hi Geert,
Hi Michael,
On Tue, Mar 25, 2014 at 8:53 AM, schmitz
wrote:
How can I delay the call to atari_stram_reserve_pages() until after VM init,
but before driver initcalls?
arch_initcall()?
subsys_initcall()?
Right - I'll try and see what works. Could only think of
device_in
Hi Michael,
On Tue, Mar 25, 2014 at 8:53 AM, schmitz
wrote:
> How can I delay the call to atari_stram_reserve_pages() until after VM init,
> but before driver initcalls?
arch_initcall()?
subsys_initcall()?
Or you can delay the ioremap() until the first caller of atari_stram_alloc()?
If the ker
Hi Geert,
Hi Michael,
On Sat, Mar 15, 2014 at 7:29 PM, schmitz
wrote:
The problem is - it dies when calling ioremap:
stram_virt_offset = ioremap(stram_pool.start,
resource_size(&stram_pool) - stram_pool.start);
Why do you subtract stram_
Hi Michael,
On Sat, Mar 15, 2014 at 7:29 PM, schmitz
wrote:
> The problem is - it dies when calling ioremap:
>
>stram_virt_offset = ioremap(stram_pool.start,
>resource_size(&stram_pool) - stram_pool.start);
Why do you subtract stram_pool.start from
schmitz writes:
> Should work - did you change anything else than swapping the meminfo chunk
> order?
Only renaming [LILO]SkipSTRAM to [LILO]LoadToFastRAM.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for s
Stefan,
In that case, it might be sufficient to change the fixed Videl base
address to a variable one in the atafb driver, and perhaps use kmalloc
instead of stram_alloc to allocate the frame buffer. If someone with
access to this hardware is interested in giving this a try, I'd be happy
to elab
Hi Andreas,
schmitz writes:
Andreas,
works, but doesn't quite do what I need - to emulate the behaviour of
ataboot, the ST-RAM chunk needs to be added after the FastRAM one, not
omitted.
Does that work?
Should work - did you change anything else than swapping the meminfo
chunk
Ingo,
Am 18.03.2014 um 01:59 schrieb schmitz :
Stefan - Geert's ioremap trick does not absolve us from having ST-RAM mapped in
the first place. This is shaping up more complex than I thought.
Would it work when SPARSEMEM would be available on m68k? I thought that's what it's all abou
Am 18.03.2014 um 01:59 schrieb schmitz :
> Stefan - Geert's ioremap trick does not absolve us from having ST-RAM mapped
> in the first place. This is shaping up more complex than I thought.
Would it work when SPARSEMEM would be available on m68k? I thought that's what
it's all about: making dif
Andreas,
works, but doesn't quite do what I need - to emulate the behaviour of
ataboot, the ST-RAM chunk needs to be added after the FastRAM one, not
omitted.
I'll play a bit with your patch, should be easy to modify unless I'm
missing something.
Stefan - Geert's ioremap trick does not abs
Hi Michael,
>> git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
> Fails with:
>
> schmitz@hobbes:~/kexec-tools$ make
> gcc -g -O2 -fno-strict-aliasing -Wall -Wstrict-prototypes -I./include
> -I./util_lib/include -Iinclude/ -I./kexec/arch/m68k/include -c -MD -o
> kexec/k
Geert,
git clone
git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
cd kexec-tools
./bootstrap
./configure
make install
It has less build requirements than ARAnyM ;-)
Missing typedefs for __u16, __u32, __be16 and __be32 (the former two
being present in /usr/include/asm/types
Geert,
Does the hack below (not even compile-tested) work? It maps pool_size
(default 1 MiB) of ST-RAM and makes the pool use that.
Sort of - boots with kernel in ST-RAM, but nothing shown on the
screen. SCSI appears to allocate DMA-able memory though:
Turns out the test for kernel in S
Geert,
Does the hack below (not even compile-tested) work? It maps pool_size
(default 1 MiB) of ST-RAM and makes the pool use that.
Sort of - boots with kernel in ST-RAM, but nothing shown on the
screen. SCSI appears to allocate DMA-able memory though:
Turns out the test for kernel in
Geert,
Hi Michael,
On Thu, Mar 13, 2014 at 7:35 AM, schmitz
wrote:
(Neither do I have kexec tools yet - nice plug though, Geert! I definitely
need to play with kexec.)
git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
cd kexec-tools
./bootstrap
./configure
mak
Geert,
Sort of - boots with kernel in ST-RAM, but nothing shown on the
screen. SCSI
appears to allocate DMA-able memory though:
Ignoring memory chunk at 0x0:0xe0 before the first chunk
Haha, you still have it in the bootinfo. Fortunately Linux doesn't use
it ;-)
No idea how to suppr
schmitz dixit:
>> BOOTSTRA.TTP works on TOS/MiNT, IIRC.
> True, I just don't have TOS or MiNT installed on any ARAnyM disk image I have.
Just tell ARAnyM to use a host directory as C: for TOS/MiNT.
It will not exist in Linux, but by then we won’t need it either ☺
(I’ve just used Afros as a base
Hi Michael,
On Thu, Mar 13, 2014 at 9:22 AM, schmitz
wrote:
>> Does the hack below (not even compile-tested) work? It maps pool_size
>> (default 1 MiB) of ST-RAM and makes the pool use that.
>
> Sort of - boots with kernel in ST-RAM, but nothing shown on the screen. SCSI
> appears to allocate DMA
Geert
(Neither do I have kexec tools yet - nice plug though, Geert! I definitely
need to play with kexec.)
git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
cd kexec-tools
./bootstrap
./configure
make install
It has less build requirements than ARAnyM ;-)
Othe
Geert,
On Tue, 11 Mar 2014, Michael Schmitz wrote:
People that need to use ST RAM because the have too little TT RAM, could
still use the -s kernel option and enable ST RAM for kernel.
Perhaps an option to specify the video RAM adress space is easier to
implement to the existing memory model
Andreas,
I haven't found a way to tell ARAnyM to load the kernel to FastRAM, so
this will need testing on real hardware,
Can you try this patch? Use [LILO] SkipSTRAM = true to enable.
Thanks for providing this patch - I will have to check whether I can get
all packages I need to com
Hi Michael,
On Thu, Mar 13, 2014 at 7:35 AM, schmitz
wrote:
> (Neither do I have kexec tools yet - nice plug though, Geert! I definitely
> need to play with kexec.)
git clone git://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git
cd kexec-tools
./bootstrap
./configure
make install
It h
Thorsten,
Michael Schmitz dixit:
I haven't found a way to tell ARAnyM to load the kernel to FastRAM, so this
will need testing on real hardware,
BOOTSTRA.TTP works on TOS/MiNT, IIRC.
True, I just don't have TOS or MiNT installed on any ARAnyM disk image I
have.
(Neither do I h
Michael Schmitz dixit:
> I haven't found a way to tell ARAnyM to load the kernel to FastRAM, so this
> will need testing on real hardware,
BOOTSTRA.TTP works on TOS/MiNT, IIRC.
bye,
//mirabilos
--
Owāte Jong… isch owāte disch gleisch…
Ich kenn nur Oblate
Lernenz Platt
Ich bin zu dick für Pl
Geert Uytterhoeven writes:
> On Wed, Mar 12, 2014 at 8:09 AM, Michael Schmitz
> wrote:
>> I haven't found a way to tell ARAnyM to load the kernel to FastRAM, so this
>> will need testing on real hardware,
>
> You can, with kexec and a separate bootinfo file that contains TT RAM only.
Though it
On Wed, Mar 12, 2014 at 8:09 AM, Michael Schmitz
wrote:
> I haven't found a way to tell ARAnyM to load the kernel to FastRAM, so this
> will need testing on real hardware,
You can, with kexec and a separate bootinfo file that contains TT RAM only.
Gr{oetje,eeting}s,
Geer
Stefan,
Adding an option to the atafb video driver make use of the SuperVidel
hardware would be the easiest option. The SuperVidel base address is
fixed, and it can use any chunk of FastRAM for frame buffer,
presumably?
The SuperVidel has 128MB Video RAM (DDR2 SDRAM):
Thanks, that'll make i
Geert,
might well work, and can be conditionalized to handle pool allocation
the old way if the kernel is in ST-RAM, and your way otherwise. Thanks
for coming up with this hack.
There's no memfile - ST-RAM is always ignored by mem_init if the kernel
is in FastRAM.
I haven't found a way
Am 11.03.2014 07:14, schrieb Michael Schmitz:
Stefan,
Yes, the Falcon IDE is not too fast. But loading the OS needs 10 minutes.
That can't honestly be the fault of a slow IDE bus.
Just saying your comparison wasn't entirely fair.
Ah, okay :) It was Amiga against Atari - never entirely fair,
On Tue, 11 Mar 2014, Michael Schmitz wrote:
> > People that need to use ST RAM because the have too little TT RAM, could
> > still use the -s kernel option and enable ST RAM for kernel.
> >
> > Perhaps an option to specify the video RAM adress space is easier to
> > implement to the existing memor
Stefan,
Yes, the Falcon IDE is not too fast. But loading the OS needs 10
minutes.
That can't honestly be the fault of a slow IDE bus.
Just saying your comparison wasn't entirely fair.
I wouldn't mind losing all ST RAM. The option to NOT load kernel into
ST RAM is there, but it simply hangs.
Hi Michael,
Yes, the Falcon IDE is not too fast. But loading the OS needs 10 minutes.
That can't honestly be the fault of a slow IDE bus.
I wouldn't mind losing all ST RAM. The option to NOT load kernel into
ST RAM is there, but it simply hangs. I guess this is because of the
Atari tries to allo
Stefan,
your point regarding ST-RAM performance is well taken - in fact, it has
been raised before. Repeatedly.
What keeps us from placing the kernel in TT--RAM is the simple fact
that under the current memory model used by m68k, we will lose all of
ST-RAM for use by either the kernel or use
Sorry, this went into the thread here, was aimed to be a new one.
Stefan
--
To UNSUBSCRIBE, email to debian-68k-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/531a0881.7010...@osnanet.de
Hi debian/68k people,
i know, while using Aranym for running debian-68k on Atari-compatible
machine, it doesn't make a noticeable (if any) performance difference to
boot the kernel with -s option (put Kernel in ST-RAM).
But if you run it on a real 680x0 machine, which in my case is a
Falcon w
Hi debian/68k people,
i know, while using Aranym for running debian-68k on Atari-compatible
machine, it doesn't make a noticeable (if any) performance difference to
boot the kernel with -s option (put Kernel in ST-RAM).
But if you run it on a real 680x0 machine, which in my case is a
Falcon w
37 matches
Mail list logo
