From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philippe Gerum In-Reply-To: <45CAEB8C.40000@domain.hid> References: <45CAE190.6020404@domain.hid> <1170926285.20614.7.camel@domain.hid> <45CAEB8C.40000@domain.hid> Content-Type: text/plain Date: Thu, 08 Feb 2007 10:30:40 +0100 Message-Id: <1170927041.20614.9.camel@domain.hid> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: Philippe Gerum Subject: [Xenomai-core] Re: Fixed two timer base regressions Reply-To: rpm@xenomai.org List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai-core On Thu, 2007-02-08 at 10:21 +0100, Jan Kiszka wrote: > Philippe Gerum wrote: > > On Thu, 2007-02-08 at 09:38 +0100, Jan Kiszka wrote: > >> Hi Philippe, > >> > >> the "trivial" bugs are fixed already: see #2152 for the reason why > >> rt_dev_read timeouts took too long (the timer mode was ignored by > >> xnsynch_sleep_on), > > > > Ok. > > > >> and I also found a yet invisible bug in > >> rtdm_toseq_init that would have picked the wrong time base (#2153). > >> > > > > Using xnpod_current_thread()'s time base in rtdm_toseq_init() will > > always pick the master one when called over a secondary mode context, > > which according to the doc, is allowed. Is this intended? > > rtdm_toseq_init will only be called over primary context, it belongs > into the same context as rtdm_mutex_timedlock, rtdm_sem_timeddown, etc. > So the doc needs fixing, I guess. -- Philippe.