bug-lispm
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: usim breakage


From: Mete Balci
Subject: Re: usim breakage
Date: Wed, 8 Jan 2025 14:15:56 +0100

Yes I know about the issue but not sure about the reason and the solution yet. I need to experiment a bit and maybe also try different renderers.

Mete

On Wed, Jan 8, 2025 at 12:55 PM Björn Victor <bjorn@victor.se> wrote:
Thanks! I just get two writes and two reads now:
usim-sdl3: xbus: write unknown paddr:17200000 pn:00036400 v:1
usim-sdl3: xbus: read unknown paddr:17200000 pn:00036400
usim-sdl3: xbus: write unknown paddr:17200000 pn:00036400 v:1
usim-sdl3: xbus: read unknown paddr:17200000 pn:00036400

and I can boot my old loadband. Thanks!

A separate issue though: the X11 backend is still much sharper than the sdl2 and sdl3 backends. In SDL2, setting the scale_filter to nearest makes it equally sharp (I suggest this to be the default when using fixnum scaling!). 

Patching sdl3_video_init() in sdl3-video.c to use SDL_SCALEMODE_NEAREST  doesn't seem to have the same effect - is this a "known issue" or is there a workaround?

-- Björn


On 2025-01-08 11:51, Mete Balci wrote:
can you update trunk and retry ? I checked all 303,302,301,300 distribution images with sdl3. You should see a few (~10) unknown paddr messages but definitely not too many.

On Wed, Jan 8, 2025 at 11:39 AM Björn Victor <bjorn@victor.se> wrote:
On 2025-01-08 11:19, Björn Victor wrote:
> On 2025-01-08 11:14, Alfred M. Szmidt wrote:
>> Help?
>>
>> Is this trunk? It works for both me and mete ..
>
> It is trunk. It works better (boots) with the new 303 disk image from
> tumbleweed, but why not with the old (300)?
>
> I'll get back when I've tested more.

If I copy "my" old loadband from my old disk to the new (using
diskmaker) and disk-restore it, I get the "gazillion printout" behaviour.

If I copy the old 300.0 distribution loadband from my old disk to the
new (using diskmaker) and disk-restore it, usim first halts, but the
next time I try, it also goes into "read unknown paddr" mode.

I don't think it should?

Does this happen for you (the 300.0 case)?

-- Björn




reply via email to

[Prev in Thread] Current Thread [Next in Thread]