Inducing delay with out a blocking wait

Thu, 2012-01-12 09:45

#2

trixie

Offline

Last seen: 1 week 2 days ago

Joined: 2011-02-03 13:58

Re: Inducing delay with out a blocking wait

You might try waiting for IDCMP_INTUITICK messages. Intuiticks are generated about every 1/10 of a second. The solution would require going into a Wait() IDCMP loop, counting the required number of intuiticks, and acting accordingly.

AmigaOne X5000-020 / 2GB RAM / Sapphire Pulse Radeon RX 560 / AmigaOS 4.1 Final Edition Update 2

Thu, 2012-01-12 17:21

(Reply to #2) #3

tekmage

Offline

Last seen: 2 years 8 months ago

Joined: 2011-10-09 03:19

Thanks Trixie, I'll take a

Thanks Trixie,

I'll take a look at the docs for IDCMP_INTUITICK and see how that works.

Cheers,
Bill

Fri, 2012-01-20 09:33

(Reply to #3) #4

tekmage

Offline

Last seen: 2 years 8 months ago

Joined: 2011-10-09 03:19

Hi trixie, Where are the new

Hi trixie,

Where are the new laws posted?

Fri, 2012-01-20 16:13

#5

hypex

Offline

Last seen: 1 month 3 weeks ago

Joined: 2011-09-09 16:20

You could also use

You could also use timer.device. Not as easy as a library but it is the standard Amiga way of doing it. We could use an alarm or timer function for OS4 right now!

You are right to look for a better way than Delay(). Internally this opens timer.device on every call so not very efficient! Still not fixed in OS4.

Fri, 2012-01-20 18:09

(Reply to #5) #6

trixie

Offline

Last seen: 1 week 2 days ago

Joined: 2011-02-03 13:58

Re: Inducing delay with out a blocking wait

@tekimage

Hi trixie,

Where are the new laws posted?

What laws??? :-)

AmigaOne X5000-020 / 2GB RAM / Sapphire Pulse Radeon RX 560 / AmigaOS 4.1 Final Edition Update 2

Sat, 2012-01-21 08:28

(Reply to #6) #7

salass00

Offline

Last seen: 3 weeks 2 days ago

Joined: 2011-02-03 11:27

@tekmage Open and close

@tekmage

Open and close timer.device:

struct MsgPort *TimerPort = NULL;
struct TimeRequest *TimerIO = NULL;
BOOL TimerInUse = FALSE;
 
BOOL OpenTimerDevice (void) {
    TimerPort = IExec->AllocSysObject(ASOT_PORT, NULL);
    TimerIO = IExec->AllocSysObjectTags(ASOT_IOREQUEST,
        ASOIOR_ReplyPort, TimerPort,
        ASOIOR_Size,      sizeof(struct TimeRequest),
        TAG_END);
    if (TimerIO) {
        if (IExec->OpenDevice("timer.device", UNIT_MICROHZ,
            (struct IORequest *)TimerIO, 0) == IOERR_SUCCESS)
        {
            return TRUE;
        }
        TimerIO->Request.io_Device = NULL;
    }
    return FALSE;
}
 
void CloseTimerDevice (void) {
    if (TimerIO && TimerIO->Request.io_Device) {
        if (TimerInUse) {
            IExec->AbortIO((struct IORequest *)TimerIO);
            IExec->WaitIO((struct IORequest *)TimerIO);
        }
        IExec->CloseDevice((struct IORequest *)TimerIO);
    }
    IExec->FreeSysObject(ASOT_IOREQUEST, TimerIO);
    IExec->FreeSysObject(ASOT_PORT, TimerPort);
}

Start a timer request:

TimerIO->Request.io_Command = TR_ADDREQUEST;
TimerIO->Time.Seconds = seconds;
TimerIO->Time.Microseconds = microseconds;
IExec->SendIO((struct IORequest *)TimerIO);
TimerInUse = TRUE;

Then in your event loop:

signals_received = IExec->Wait((1 << TimerPort->mp_SigBit)|other_signals_to_wait_for);
if (signals_received & (1 << TimerPort->mp_SigBit)) {
    IExec->WaitIO((struct IORequest *)TimerIO);
    TimerInUse = FALSE;
    Printf("Timer request is finished\n");
}

Of course if you just need a more accurate version of IDOS->Delay() you can just use IExec->DoIO() (returns when the specified time has elapsed):

TimerIO->Request.io_Command = TR_ADDREQUEST;
TimerIO->Time.Seconds = seconds;
TimerIO->Time.Microseconds = microseconds;
IExec->DoIO((struct IORequest *)TimerIO);

Wed, 2012-01-25 08:16

(Reply to #7) #8

tekmage

Offline

Last seen: 2 years 8 months ago

Joined: 2011-10-09 03:19

Thanks salass00. AlexC had a

Thanks salass00.

AlexC had a simpler example:

#include <proto/exec.h>
#include <proto/timer.h>
#include <proto/dos.h>
 
int main(int argc,char **argv)
{
int32 result = 0;
ITimer->MicroDelay(1000);
return(result);
}

To compile the above lib auto is used to open the device:

gcc -o microdelay microdelay.c -lauto

Stuck on trying to figure out the least amount of stuff to get the above to compile without libauto. Looking at timer.xml everything looks like a library but OpenLibrary does not seam to do it.

Wed, 2012-01-25 09:09

(Reply to #8) #9

salass00

Offline

Last seen: 3 weeks 2 days ago

Joined: 2011-02-03 11:27

Don't use MicroDelay() in

Don't use MicroDelay() in general code as it's polling (ties up the CPU while it waits). MicroDelay() should only ever be used for very small delays in places where multitasking is disabled or in interrupt code. As stated in the AutoDocs MicroDelay() is only really useful for driver writers that may need to use it for the simple reason that it doesn't need multitasking in order to work.

Wed, 2012-01-25 09:18

(Reply to #9) #10

salass00

Offline

Last seen: 3 weeks 2 days ago

Joined: 2011-02-03 11:27

If you need an usleep() type

If you need an usleep() type function you can just use:

void USleep (uint32 microseconds) {
    TimerIO->Request.io_Command = TR_ADDREQUEST;
    TimerIO->Time.Seconds = microseconds / 1000000;
    TimerIO->Time.Microseconds = microseconds % 1000000;
    IExec->DoIO((struct IORequest *)TimerIO);
}

Or of course if you're not concerned about writing using AmigaOS API functions you can just use usleep() from newlib (works same as MicroDelay() only it doesn't use a polling loop, instead it uses timer.device in more or less the same way as I wrote above).

#include <unistd.h>
 
int main(int argc,char **argv)
{
int result = 0;
usleep(1000);
return(result);
}

Fri, 2012-01-27 08:56

(Reply to #10) #11

hypex

Offline

Last seen: 1 month 3 weeks ago

Joined: 2011-09-09 16:20

Does newlib usleep() also

Does newlib usleep() also open up timer.device and required resources when it is called every time like Delay()O or is it cleaner?

Fri, 2012-01-27 10:05

(Reply to #11) #12

salass00

Offline

Last seen: 3 weeks 2 days ago

Joined: 2011-02-03 11:27

@hypex Does newlib usleep()

@hypex

Does newlib usleep() also open up timer.device and required resources when it is called every time like Delay()O or is it cleaner?

You do know that AmigaOS since version 1.0 caches libraries and devices so that they aren't reloaded every time there is an OpenDevice() or OpenLibrary()?

When a library or device is already in memory (timer.device is always in memory since it's in Kickstart) it's pretty much only a quick list lookup for "timer.device" and incrementing some open counters so there really isn't much overhead, plus opening/closing libraries/devices only when they are needed has the advantage that the OS can expunge them when they are not needed if it needs to create free memory for something else.

Fri, 2012-01-27 16:26

(Reply to #12) #13

hypex

Offline

Last seen: 1 month 3 weeks ago

Joined: 2011-09-09 16:20

Yes I do know they are

Yes I do know they are resident and maybe that's a big problem with AmigaOS. I have seen applcations call OS functions and use a snopping tool to watch hundreds of fonts being opened and devices. Delay() is one for this. It looks unnecessary and not very efficient to always allocate memory for these structures and open these resources when ever a function is called. Everything should be cached for futher use, not just a library.

I think this sort of thing would contribute to AmigaOS slowing down and in real use AmigaOS isn't fast any more. It can and will choke at a simple mouse move these days.

Search form

User login