Page 24 of 26
Re: TF1260 New Firmware Alpha Released!
Posted: 20 Mar 2023 12:56
by supaduper
FYI , the Screen resolution say like hi-res and the number of colours you have selected can influence the mips so reduce those and you will see different speeds :)
remember more system resources used like colours used and screeen depth will always affect these mip figures
Re: TF1260 New Firmware Alpha Released!
Posted: 20 Mar 2023 15:36
by PainDictator
supaduper wrote: 20 Mar 2023 12:56
FYI , the Screen resolution say like hi-res and the number of colours you have selected can influence the mips so reduce those and you will see different speeds :)
remember more system resources used like colours used and screeen depth will always affect these mip figures
I know, that is why all Tests where done using a single bitplane pal highres noninterlaced screen. AFAIR highres with Up to two Planes will Not use additional Chip RAM cycles.
Re: TF1260 New Firmware Alpha Released!
Posted: 02 May 2023 12:25
by AmigaDweeb
Hmmm interesting stuff, as this thread appears directly related to my own thread and question here today
viewtopic.php?f=101&t=6273
Re: TF1260 New Firmware Alpha Released!
Posted: 11 Jun 2023 20:06
by arek0xff
thanks for great card!
I'm wondering if it would be possible to add a software switch "compatibility mode" which would disable 060 CPU and leave only FAST ram? That would be great option as 060 is still problematic for older games.
thanks
Re: TF1260 New Firmware Alpha Released!
Posted: 11 Jun 2023 20:18
by terriblefire
arek0xff wrote: 11 Jun 2023 20:06
thanks for great card!
I'm wondering if it would be possible to add a software switch "compatibility mode" which would disable 060 CPU and leave only FAST ram? That would be great option as 060 is still problematic for older games.
thanks
Unfortunately the 020 can only address 8Mb of fast ram and its not capable of talking to the SDRAM
Re: TF1260 New Firmware Alpha Released!
Posted: 13 Jun 2023 15:06
by CrazyC
Just wondering if there was any news re a new version of the ehide driver, as TF mentioned this earlier in the thread as a possibility.
I have held off upgrading from 3.2 to 3.2.2.1 but am going to do it shortly alongside flashing my tf1260 firmware and will order new physical roms at that point, and was wondering whether or not to hold off a bit longer so as to include a newer ehide.
Cheers
Re: TF1260 New Firmware Alpha Released!
Posted: 13 Jun 2023 21:07
by terriblefire
CrazyC wrote: 13 Jun 2023 15:06
Just wondering if there was any news re a new version of the ehide driver, as TF mentioned this earlier in the thread as a possibility.
I have held off upgrading from 3.2 to 3.2.2.1 but am going to do it shortly alongside flashing my tf1260 firmware and will order new physical roms at that point, and was wondering whether or not to hold off a bit longer so as to include a newer ehide.
Cheers
I have ehide 1.2 but its entirely up to
@erique when he releases it.
Re: TF1260 New Firmware Alpha Released!
Posted: 13 Jun 2023 21:30
by CrazyC
Ooh, any particular changes or just a gradual improvent or bug fix type version change?
Re: TF1260 New Firmware Alpha Released!
Posted: 15 Jun 2023 10:49
by terriblefire
CrazyC wrote: 13 Jun 2023 21:30
Ooh, any particular changes or just a gradual improvent or bug fix type version change?
Its a lot of minor fixes really.
Re: TF1260 New Firmware Alpha Released!
Posted: 05 Jul 2023 23:38
by erique
terriblefire wrote: 13 Jun 2023 21:07
I have ehide 1.2 but its entirely up to @erique when he releases it.
Old man moves slowly.. :coffee:
ehide_1.2_9c4ac27.tar.gz
Code: Select all
ehide 1.2 (04.7.2023) TF IDE Driver (9c4ac27)
[BUGFIX] Formatting a partition (using TD_FORMAT) could hang the device driver.
[BUGFIX] When using removable media in combination with TD_ADDCHANGEINT, a notification callback could sometimes be missed.
[BUGFIX] The expansion.library/ConfigDev was not properly initialized, causing HDToolBox to reload the driver multiple times in certain scenarios.
[BUGFIX] The error reporting (SCSI Key Code Qualifier), in case of an IDE/ATA command failure, was mostly incorrect.
[CHANGE] Executing 'ehide.device' from CLI is now handled gracefully; return code = -1.
[CHANGE] Media reporting a zero cylinder size is now considered bad/faulty, and ignored.
[CHANGE] The PIO read-loop now stores data in 16 bytes chunks (using movem.l), making the read-loop tighter.
[CHANGE] The device driver ROMTAG wasn't pointing to the end of the code segment, causing unnecessary work during ROMTAG scanning.
[CHANGE] About 15% smaller code size (~2k less)
It could also be that I managed to add some new fresh bugs; I'm sure you'll tell me if that's the case ;)