Sponsored Content
Full Discussion: Skin for PDA
The Lounge What is on Your Mind? Skin for PDA Post 54871 by Neo on Thursday 26th of August 2004 03:39:59 PM
Old 08-26-2004
It might be time to uograde to vB 3.x

I think PDA access is critical .....

Thoughts?
 

2 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Linux/Unix PDA

Is it possible to get a handheld pc/pda with Linux or Unix installed. Most of them seem to come with something called Palm OS or Windows. (7 Replies)
Discussion started by: jacx2
7 Replies

2. Solaris

Palm PDA

Anyone found a driver to work with Palm PDAs with a USB cradle? My system is: Solaris 9 Ultra 10 workstation Generic USB controller (works with other devices) Palm M505 J-Pilot Pilot-link Thanks for any help. Matt (4 Replies)
Discussion started by: matteguru
4 Replies
CRITICAL_ENTER(9)                                          BSD Kernel Developer's Manual                                         CRITICAL_ENTER(9)

NAME
critical_enter, critical_exit -- enter and exit a critical region SYNOPSIS
#include <sys/param.h> #include <sys/systm.h> void critical_enter(void); void critical_exit(void); DESCRIPTION
These functions are used to prevent preemption in a critical region of code. All that is guaranteed is that the thread currently executing on a CPU will not be preempted. Specifically, a thread in a critical region will not migrate to another CPU while it is in a critical region. The current CPU may still trigger faults and exceptions during a critical section; however, these faults are usually fatal. The critical_enter() and critical_exit() functions manage a per-thread counter to handle nested critical sections. If a thread is made runnable that would normally preempt the current thread while the current thread is in a critical section, then the preemption will be deferred until the current thread exits the outermost critical section. Note that these functions are not required to provide any inter-CPU synchronization, data protection, or memory ordering guarantees and thus should not be used to protect shared data structures. These functions should be used with care as an infinite loop within a critical region will deadlock the CPU. Also, they should not be inter- locked with operations on mutexes, sx locks, semaphores, or other synchronization primitives. One exception to this is that spin mutexes include a critical section, so in certain cases critical sections may be interlocked with spin mutexes. HISTORY
These functions were introduced in FreeBSD 5.0. BSD October 5, 2005 BSD
All times are GMT -4. The time now is 06:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy