Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
216 user(s) are online (120 user(s) are browsing Forums)

Members: 1
Guests: 215

MigthyMax, more...

Headlines

Forum Index


Board index » All Posts (joerg)




Re: Porting to AmigaOS4 thread
Just can't stay away
Just can't stay away


@LiveForIt
AmigaOS doesn't have any problems with fragmented stacks, even porting Rust to AmigaOS, the programming language used for example by the current FireFox versions, would be much less of a problem than for example porting the Linux version was to BSD Unixes.
AmigaOS always supporting stack swapping, for example the ancient IExec->StackSwap() and newer replacement functions in Exec(SG).

Go to top


Re: Porting to AmigaOS4 thread
Just can't stay away
Just can't stay away


@Raziel
Quote:
why not simply enhance the stack where needed?
the OS should be capable of providing on-the-fly stack enhancement, shouldnt it?
The C compiler (at least GCC, not sure about VBCC) has an option to increase the stack size automatically when required, but AmigaOS 4.x doesn't support that and will crash if the stack size is too small.
The "stack cookie" is only one of the options, there is the shell stack size or the Workbench Icon stack size as well, and the largest one of all options will be used, but if all of them are too small for a given program it will crash on AmigaOS 4.x.
The stack can't be swapped out by the pager, if you'd use 2 GB stack any program will crash immediately because of the 2 GB limit of a single, ancient Exec(SG) function. Using 1 GB may work for most software, but you'll only have the other 1 GB available for anything else.

Go to top


Re: About off topic news on Amigans
Just can't stay away
Just can't stay away


@orgin
Quote:
I emplore everyone who has not yet done so to read the full contents of the Statement of Intent
The Statement of Intent needs an update. For example does "Emulation of 68k AmigaOS" and "68k AmigaOS, compatible software and hardware"
- include Hyperion's PiracyOS ("AmigaOS" versions 3.1.x/3.2.x, which in large parts are based on stolen AmigaOS 4.x sources)?
- include something like the "THE500 Mini", which is more or less "68k AmigaOS compatible hardware", and can run some old AmigaOS 68k games, but is no classic Amiga hardware at all, or AmigaKit's "A600GS", which doesn't use anything AmigaOS related but AROS/m68k + Enhancer Software V46, running on an ARM CPU via Emu68k, instead?
- include something like the Apollo V4 systems (no Amiga, not even m68k compatible, hardware but incompatible emulation) with ApolloOS (not AmigaOS but AROS based)?

Go to top


Re: Opening the 1st bootmenu automatically (X5000)
Just can't stay away
Just can't stay away


@Gregor
I don't know if you can disable auto-booting the default completely, but if you use something like
setenv amigabootmenu_timeout 30
saveenv
you have enough time to change it to another boot option.

Go to top


Re: Updater tool: latest releases and updates
Just can't stay away
Just can't stay away


@Tuvok
Quote:
Would it be possible to check the database of the updater utility?
There are a couple of entries which are not up-to-date. AmiDVD shows version 1.51 remote but the local one that I installed from Emhancher is 1.53.
I don't remember which version of AmiDVD was included in the last public version of the Enhancer Software, but it's definitely not 1.53.
Versions 1.53 and 1.54 are newer, 1.54 (or maybe 1.55) will be included in Enhancer Software 2.3, which isn't released yet.

Go to top


Re: Best way to clone HDD?
Just can't stay away
Just can't stay away


@geennaam
It should work the same way using an Amiga RDB instead of a MBR or GPT.
Unless you store an AmigaOS <= 3.x/m68k filesystem binary in it as well, or you are using more than 3 partitions, the RDB should be <= 4 KB.
When partitioning it with MediaToolBox, or similar AmigaOS tools, add a non-sense partition, for example using DOSType 0x01020304, reserving the space required for the U-Boot image (or simply 4 GB as that's IIRC the min. size of SD cards supported on the X5000) and use the rest of it for a FFS or SFS boot/kickstart partition.

Edit: There is a DOSType for unused/unsupported by AmigaOS space: "RESV", use that (0x52465156) instead of something like 0x01020304.

Edit2: Sorry, I don't know how to boot from the SD card, but if the X-5000 can boot a Linux kernel + initrd from it it can boot the AmigaOS amigaboot.ub + kernel/kickstart modules from it as well.


Edited by joerg on 2024/1/26 20:20:17
Edited by joerg on 2024/1/26 20:25:17
Edited by joerg on 2024/1/26 20:41:01
Go to top


Re: Best way to clone HDD?
Just can't stay away
Just can't stay away


@geennaam additionally to what @sailor wrote:

If you are using a device/partition/filesystem which can be accessed by both the firmware and AmigaOS for the boot partition you may have to use BootDevice in the kicklayout.
For example if your nvme Workbench:/SYS: partition is "DH0:" create a text file "Kickstart/BootDevice" on the SD boot partition with the contents "DH0" and add
MODULE Kickstart/BootDevice
to the kicklayout.
Without it, depending on firmware/bootloader, AmigaOS might try to use your small SD boot/kickstart partition as Workbench:/SYS: partition, instead of the one on the nvme.

Go to top


Re: Best way to clone HDD?
Just can't stay away
Just can't stay away


@geennaam
Quote:
This is not trivial. Next to the new NGFS, you'll also need a new amigaboot. Otherwise you cannot boot amigaos on NGF/01
Even with an old amigaboot.(of|ub) or SLB_v2 you should be able to use newer versions of NGFS.
You'll have to use a FFS, SFS or NGF\0 boot partition with the kickstart files, incl. the new NGFS version, loaded by U-Boot/CFE/SmartFirmware via SLB_v2 or amigaboot, but you can use NGF\1 for the Workbench: and all other partitions only accessed by AmigaOS but not by the firmware/SLB.

Go to top


Re: Pciutils - lspci and setpci
Just can't stay away
Just can't stay away


@flash
You probably can do the same with them as with the firmware, as described for example on https://www.amigaportal.cz/node/158086 , to use PCIe gfx cards with a PCI->PCIe bridge, but using setpci on AmigaOS instead of using the U-Boot/SmartFirmware PCI commands to change/fix some settings has no advantage, instead you'd have the same problem as on a Sam4x0/X1000/X5000 with a RX card and U-Boot: Only AmigaOS itself works after it was booted, but if booting AmigaOS doesn't work for some reason you can't access the firmware to fix it without using a serial terminal, or replacing the gfx card with an older one supported by U-Boot/SmartFirmware.

Go to top


Re: MPlayer 1.5 released!
Just can't stay away
Just can't stay away


@ktadd
You could still change what the keys should do in MPlayer's input.conf, but just mapping a few, common SET1/HID keys to the MPlayer's ones would be a lot easier than adding support for the possibility to remap all possible 64k key codes of IDCMP_EXTENDEDKEYBOARD.

Go to top


Re: Best way to clone HDD?
Just can't stay away
Just can't stay away


@drHirudo
Quote:
dd doesn't care about filesystem, partition table, etc..
Which is a big problem...

Quote:
It simply copies everything and I had case where I used the dd-ed image directly under QEmu without any issue.

Is there such utility like dd for Amiga?
Of course there are dd ports, and similar tools, but unless you are copying from/to identical disks it wont work for example for copying SFS partitions.
SFS's root blocks include the numbers of the first and last byte of the partition on the HD and if they don't match with the first/last byte of the (target) drive it wont mount the partition.

You get similar problems when dd'ing complete disks, the AmigaOS RDB includes the size of the disk. Copying to a smaller one is impossible anyway, on any OS, but on AmigaOS copying to a larger one will only use the size of the smaller source disk and you can't use the rest of the larger target. Unless you re-partition it, but that will delete all existing partitions...

Go to top


Re: MPlayer 1.5 released!
Just can't stay away
Just can't stay away


@ktadd
Quote:
As Joerg stated, Non VANILLA or RAWKEYS can't be mapped
Maybe adding support for mapping the complete IDCMP_EXTENDEDKEYBOARD codes to MPlayer's input.conf would be a lot of work, but adding some defaults for the most common multimedia keys (I don't remember if they are in subclass SET1 or HID), incl. volume +/-, pause/play, forward/backward, etc., in MPlayer should be easy.

Go to top


Re: MPlayer 1.5 released!
Just can't stay away
Just can't stay away


@Gregor
Quote:
Is it possible to use the multimedia keys (Volume down and up) of a 110-key keyboard for volume control with MPlayer?
If the keys are not mapped to Amiga RAWKEYs with the USB keymap config adding support for IDCMP_EXTENDEDKEYBOARD additionally to IDCMP_RAWKEY and IDCMP_VANILLAKEY in MPlayer is required to support such keys.

Go to top


Re: AmigaOS 4 68K emulation options
Just can't stay away
Just can't stay away


@eliyahu
Quote:
I had my reasons for asking this, but it looks like there are no parms I can set anywhere. Thanks for your answers.
If the Set68kcpu tool from OS4depot.net doesn't help for what you are trying to do you have to be more specific on what you want to achieve.

Go to top


Re: MPlayer 1.5 released!
Just can't stay away
Just can't stay away


@samo79
Current os4depot.net version seems to be SVN-r38440, with which 'p' and 'SPACE' doesn't work for pause for you either.
The version which works for you (SVN-r38423) is not, or no longer, on os4depot.net?

Go to top


Re: AmigaOS 4 68K emulation options
Just can't stay away
Just can't stay away


@eliyahu
IIRC one of the tools of OS4 itself (probably something in C:) can change the reported emulated m68k CPU, not the actual CPU emulation, but I don't remember which one nor with which options.
But there is a tool on os4depot.net as well which should do the same.

Go to top


Re: AmigaOS 4 68K emulation options
Just can't stay away
Just can't stay away


@Georg
Quote:
But I guess for example a 68k compiled webkit based web browser would not run fine in AOS4 (or MOS) 68k emulation. Despite being "system friendly" software. Or would it?
I built and tested my AmigaOS 3.9/m68k port of OWB on AmigaOS 4.1, I didn't have a 3.x/m68k system at that time any more.
Of course was working on AmigaOS 4.1 without problems, I don't know if it works on MorphOS.

@LiveForItQuote:
Portable C/C++ code compiled for 680x0 programs written in C/C++ will depend on shampooers or forbid / permit, to make struct or data atomic.
My AmigaOS 3.9 and 4.x ports of OWB don't have a single line of common code in the system specific parts, but neither one uses Forbid()/Permit() or Disable()/Enable() directly.
For the system specific mutex parts the AmigaOS 4.x ports are using the IExec->Mutex(Attempt|Obtain|Release)() functions, which are based on the PPC atomic instructions. No Forbid() or Disable() involved.
The AmigaOS 3.9 port uses the old exec (Attempt|Obtain|Release)Semaphore() functions instead, which AFAIK are using Forbid()/Permit(), or maybe even Disable()/Enable(), internally.


Edited by joerg on 2024/1/22 6:44:15
Go to top


Re: AmigaOS 4 68K emulation options
Just can't stay away
Just can't stay away


@eliyahu
Why would you want to do anything like that? For example:
Quote:
Or to not have an FPU?
Not matter if real hardware or emulated, a system without FPU is much slower, without adding any compatibility to ancient, broken software which can only work with something like UAE or Fellow. but not on AmigaOS 4.x, nor AmigaOS 3.x with a gfx card.
Emulating "more" than a 68030/68882? Why? All newer CPUs (68040, 68060) have less features and would be even slower, if they wouldn't have higher CPU clock frequencies and some additional super-scalar features on real hardware.
Not only slower, but less accurate as well. At least about 20 years ago when I ported it to AmigaOS the newlib soft-float test suite still used the results of a real 68882 FPU to report rounding errors of the implementation. No common CPU of that time, neither DEC Alpha, HP PA-RISC, IBM/Motorola/Freescale POWER/PowerPC, AMD x64, Intel x86 and XEON, MIPS, BBC/Acorn/Arm Ltd./Samsung/Huawei/etc. (Strong)ARM, nor anything else, was able to get results even close to the ones of the 80 bit 68881/2 FPU.
Additionally the clock frequency of the emulated CPU is completely irrelevant for any system with a faster host CPU than the emulated guest one...
Any "system friendly" software will work on any m68k CPU, on any gfx hardware (OCS/ECS/AGA/gfx card), no mater if real or emulated. If it doesn't it's not system friendly at all and may require ugly hacks like NallePuh or NewMode.

Go to top


Re: can
Just can't stay away
Just can't stay away


@Maijestro
You are using http://localhost/about (no encryption), the problem @328gts has is SSL/TLS related, i.e. he is trying to use something like https://localhost/about instead.

Go to top


Re: can
Just can't stay away
Just can't stay away


@Hans
Quote:
A bit embarrassing if Odyssey can't handle what was recommended SSL protocol settings years ago (e.g., min TLS 1.2, with ciphers restricted to ones that don't have known flaws).
OWB development was stopped by Pleyo in 2009 already, anything newer wont work in OWB, incl. my AmigaOS 3.x/m68k and 4.x/PPC ports and and the AROS/x86 one, and probably not in forks of it like Odyssey either.

Go to top



TopTop
« 1 2 3 4 (5) 6 7 8 ... 85 »




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project