Re: [Fwd: Re: [fpc-pascal] spin_lock]

2006-05-31 Thread Burkhard Carstens
[..] > > So what about this: > > modify your drivers sample routine that it takes a timestamp > > (time_for_next_sample) and returns a timestamp (last_sampled) > > together with your voltage value. in the sample routine take your > > spin_lock, loop until currenttime > time_for_next_sample, get you

[Fwd: Re: [fpc-pascal] spin_lock]

2006-05-31 Thread Alain Michaud
(Burkhard: my mistake. Sorry ) Hi, thank you for your message. I find it VERY usefull! I have many questions: 1-- Keep in mind that I need the processor for a period of 100 milisecond ONLY. After that, my process can be off for 10 seconds or more... Between the 'critical sections', there is p

Re: [fpc-pascal] spin_lock

2006-05-31 Thread Burkhard Carstens
Alain, I think I got a personal mail from you, but I deleted it before I realized that it's not spam (still sleepy :-). This email is for mailing list only, so any mail not coming from the mailing list is automatically dropped to the spam folder.. Could you resend it on the list? Burkhard __

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Vinzent Hoefler
On Wednesday 31 May 2006 01:04, Felipe Monteiro de Carvalho wrote: > 0.1 miliseconds is a lot of time for a modern computer. Depends. Here[tm] it's still just about 100 I/O-cycles. > My experience > is that even running on a graphical environment with other processes > running, you can get 0.1 m

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Felipe Monteiro de Carvalho
On 5/30/06, Alain Michaud <[EMAIL PROTECTED]> wrote: The problem: the problem is: even if the timing is not so critical and the the experiment does not last for long, once it has started then the processor should not leave and go answer the phone for another process... I think that most process

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Burkhard Carstens
Am Dienstag, 30. Mai 2006 22:24 schrieb Alain Michaud: > > You might want to give some more details about your "situation". > > arch? os? and why would you do this? There might be a better > > solution.. than locking the hole system for 1/5 second .. > > > > Burkhard > > Hi, > > I feel a little bit

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Joep Blom
Marc Santhoff wrote: Am Dienstag, den 30.05.2006, 16:24 -0400 schrieb Alain Michaud: I use one of those (ISA) I/O bards: I write or read from a port and control a "slow" experiment. More details about the timing: IMO this is your main problem: the rotten old board. ;) To get away

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Marc Santhoff
Am Dienstag, den 30.05.2006, 16:24 -0400 schrieb Alain Michaud: > I use one of those (ISA) I/O bards: I write or read from a port and > control a "slow" experiment. More details about the timing: IMO this is your main problem: the rotten old board. ;) To get away from "dangerous programming"

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Alain Michaud
> You might want to give some more details about your "situation". > arch? os? and why would you do this? There might be a better solution.. > than locking the hole system for 1/5 second .. > > Burkhard Hi, I feel a little bit guilty to use this list for my personal problems, but here it is:

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Burkhard Carstens
Am Dienstag, 30. Mai 2006 09:51 schrieb Jonas Maebe: > On 30 mei 2006, at 08:57, Marco van de Voort wrote: > >> This is not that easy: Is it only for UP or maybe also for SMP > >> machines? > >> Basically, for x86 the "cli" and "sti" asm instructions do > >> disable/ enable interrupts, but read abo

Re: [fpc-pascal] spin_lock

2006-05-30 Thread Jonas Maebe
On 30 mei 2006, at 08:57, Marco van de Voort wrote: This is not that easy: Is it only for UP or maybe also for SMP machines? Basically, for x86 the "cli" and "sti" asm instructions do disable/ enable interrupts, but read about it before you try. Currently, I do such stuff only inside a driv

Re: [fpc-pascal] spin_lock

2006-05-29 Thread Marco van de Voort
[ Charset ISO-8859-15 unsupported, converting... ] > Am Dienstag, 30. Mai 2006 01:05 schrieb Alain Michaud: > > Hi, > > > > would someone know how to execute: spin_lock spin_lock_init and > > spin_unlock > > > > I just want to disable the interrupts for 200 miliseconds maximum! > > This is not too

Re: [fpc-pascal] spin_lock

2006-05-29 Thread Burkhard Carstens
Am Dienstag, 30. Mai 2006 01:05 schrieb Alain Michaud: > Hi, > > would someone know how to execute: spin_lock spin_lock_init and > spin_unlock > > I just want to disable the interrupts for 200 miliseconds maximum! > This is not too long and hopefuly, my system will not crash... Well, 200 ms is abo

[fpc-pascal] spin_lock

2006-05-29 Thread Alain Michaud
Hi, would someone know how to execute: spin_lock spin_lock_init and spin_unlock I just want to disable the interrupts for 200 miliseconds maximum! This is not too long and hopefuly, my system will not crash... Does someone has any experience with this kind of situation. Sincerely Alain Mic