Pre-Announcement MiNT 1.14
Eric R. Smith
Sounds like you've added some nice features to MiNT. But please don't
release your version as "MiNT 1.14"; please use a name like "FreeMiNT 1.14"
or "FMiNT 1.14" or "XXX 1.14", where XXX is any string not equal to MiNT.
(See the MiNT copyright notice for details.)
Regards,
Eric
--
Eric R. Smith
ers...@netcom.com
Sven Karlsson
Hi!
Since the current version of MiNT is so old I have added some nice things to
1.12.5 ,skipped the bad luck (probably) of 1.13 and made a version 1.14. I
don't know if anyone else is working on MiNT. If so please mail me...
the changes are:
- VM! At last! Gives you a lot of "TT-Ram" (or Alt-ram if you prefer) at the
expense of some ST or TT-ram. I have run it some weeks now and it is very
stable
and compatible on my TT. Needs 030. Currently not compatible with 040 or 060
mmus (sorry folks.. will do that when someone wants to beta test it on their
Medusa/Hades/Eagle/DirectTT/afterburner etc..) All software that I have
tested
works without restrictions.
- Some minor bugfixes in bios routs (most notable setexc) and some patches to
make AHDI work with VM. Debuggers are more stable now under MiNT..
I will clean up the sources and then release the sources and binaries on the
web-site below. When the distribution is uploaded I will announce it. It is
probably uploaded on monday (16th of september)
This is probably the last version I will make of MiNT before I begin releasing
Fenix versions..
Regards
Sven Karlsson
---------------------------------------------------------------------------
Student of Engineering Physics at Lund Institute of Technology, Sweden
Soft- and Hardware developer @ Istari Software
Current project: Code ,an interactive development tool for video
game consoles including Editor,Debugger and Assembler
Fenix, a new OO OS for Atari compatible computers.
E-mail: f9...@efd.lth.se or tom...@df.lth.se
WWW: http://www.efd.lth.se/~f92sk
Eddy Morfan
> Since the current version of MiNT is so old I have added some nice things to
> 1.12.5 ,skipped the bad luck (probably) of 1.13 and made a version 1.14. I
> don't know if anyone else is working on MiNT. If so please mail me...
>
> the changes are:
>
> - VM! At last! Gives you a lot of "TT-Ram" (or Alt-ram if you prefer) at the
> expense of some ST or TT-ram. I have run it some weeks now and it is very
> stable
> and compatible on my TT. Needs 030. Currently not compatible with 040 or 060
> mmus (sorry folks.. will do that when someone wants to beta test it on their
> Medusa/Hades/Eagle/DirectTT/afterburner etc..) All software that I have
> tested
> works without restrictions.
> - Some minor bugfixes in bios routs (most notable setexc) and some patches to
> make AHDI work with VM. Debuggers are more stable now under MiNT..
>
Hi there,
All this sounds great, but I'd like to ask you a few questions:
- Is the memory protection feature still available ?
- What about the Falcon, did you manage to make the VDI work with VM ?!
The Falcon VDI always uses the Blitter chip, whose address bus is only 24 bits
wide, and which doesn't use the PMMU so that it cannot access data at locations
higher than $FFFFFF.
- How do the user sets the size of the VRAM and the amount of physical memory used
for the frames.
- I don't understand why you did patch AHDI, mine was working perfectly under VM
and you can set up the _FRB cookie for the ACSI transfers.
In fact, I began a MiNT VRAM implementation some months ago which is quite ready
but I didn't manage to go on the job as I didn't find the time to solve the Falcon
Blitter problem (studies...).
Regards, Eddy.
+---------------------------------------------------------------------+
| Eddy MORFAN ( Email : mor...@info.unicaen.fr ) |
+---------------------------------------------------------------------+
| Atari STf 2.5Mo |
| Atari Falcon 030/14Mo/340Mo |
+---------------------------------------------------------------------+
Gerald Haese
Hi!
> - Some minor bugfixes in bios routs (most notable setexc) and some patches
> to make AHDI work with VM. Debuggers are more stable now under MiNT..
Can I use other disk drivers than AHDI with VM. For instance HuShi,
HDDriver, CBHD ...
> - VM! At last! Gives you a lot of "TT-Ram" (or Alt-ram if you prefer) at
> the expense of some ST or TT-ram. I have run it some weeks now and it is
> very stable and compatible on my TT
Do I need a special format for swap partition(s)? How can I create one. It
would be fine, if I could use the same one like under m68k-linux ...
greetings,
Gerald
Gerald Haese
Hi!
> The swappartition only needs a special magic in the bootsector.
Can we use the same like linux?
Uses VM the whole partition? Is the old structure of this destroyed after
finishing MiNT so that I've to make a new "mkswap" under Linux?
greetings,
Gerald
Sven Karlsson
> Hi there,
>
> All this sounds great, but I'd like to ask you a few questions:
> - Is the memory protection feature still available ?
No...
> - What about the Falcon, did you manage to make the VDI work with VM ?!
> The Falcon VDI always uses the Blitter chip, whose address bus is only 24 bits
> wide, and which doesn't use the PMMU so that it cannot access data at locations
> higher than $FFFFFF.
That is no problem since the VDI always uses ST-ram. I don't expand ST-ram
since that would lead to serious HW problems.
> - How do the user sets the size of the VRAM and the amount of physical memory used
> for the frames.
The size of virtual ram is set by the partition size dedicated as backing
store. I currently take all TT-ram and all ST-ram but 4 meg as page ram.
> - I don't understand why you did patch AHDI, mine was working perfectly under VM
> and you can set up the _FRB cookie for the ACSI transfers.
>
It's because there is no scsi-dma in falcon that is capable to dma into
"TT-ram". The scsi-dma on TT can do that. So if I didn't patch the bios routs
then AHDI would have tried to dma sectors from hd into VM-ram which hangs the
TT.
Sven Karlsson
> Hi!
>
> > - Some minor bugfixes in bios routs (most notable setexc) and some patches
> > to make AHDI work with VM. Debuggers are more stable now under MiNT..
> Can I use other disk drivers than AHDI with VM. For instance HuShi,
> HDDriver, CBHD ...
I have only tested it with ahdi. But it should work with other too.
>
> > - VM! At last! Gives you a lot of "TT-Ram" (or Alt-ram if you prefer) at
> > the expense of some ST or TT-ram. I have run it some weeks now and it is
> > very stable and compatible on my TT
> Do I need a special format for swap partition(s)? How can I create one. It
> would be fine, if I could use the same one like under m68k-linux ...
The swappartition only needs a special magic in the bootsector.
Regards