From mint-bounce@lists.fishpool.fi Thu Apr 22 04:37:50 2010 Message-ID: <513044.113849418-sendEmail@descaro> From: "Helmut Karlowski" To: "mint@lists.fishpool.fi" Cc: "helmut.karlowski@ish.de" Subject: [MiNT] XaAES:Singletask-mode Date: Thu, 22 Apr 2010 08:35:11 +0000 X-Mailer: sendEmail-1.55 MIME-Version: 1.0 Content-Type: multipart/related; boundary="----MIME delimiter for sendEmail-914730.029487149" X-Antivirus: avast! (VPS 100421-1, 21.04.2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: helmut.karlowski@ish.de Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: This is a multi-part message in MIME format. To properly display this message you need a MIME-Version 1.0 compliant Email program. ------MIME delimiter for sendEmail-914730.029487149 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I've implemented a single-task-mode in XaAES. This implies: Stop all AES-Clients except the console-owner if any (e.g. toswin) Call ikbd_scan in the kernel directly not via addroottimeout in case the single-task-client disabled the timer-interrupt. To control this currently there has to be the bit 16 (0x10000) in p_flags of the relevant binary. Is it ok to use this bit? I'd like to get to know who is responsible for console, who is using /dev/xconout2. Maybe fcntl(F_GETLK) would work? This is important because the single-task-client possibly does tty-IO. It would also be possible to introduce a 'dont_stop'-config-parameter for xaaes.cnf. -Helmut ------MIME delimiter for sendEmail-914730.029487149--