From mint-bounce@lists.fishpool.fi Sat Apr 9 02:36:52 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Message-ID: <20050409003315.5858.qmail@mailcz.in.systinet.com> References: <20050408234812.2670.qmail@mailcz.in.systinet.com> In-Reply-To: From: Standa Opichal To: mint@fishpool.com Subject: Re: [MiNT] objc_draw() and other AES calls in userspace? Date: Sat, 09 Apr 2005 02:33:15 +0200 Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: opichals@seznam.cz Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.0 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Hi! OK, but how N.AES does this then (if true at all)? Standa Frank Naumann writes: > Hello! > >> While searching for the MiNT VM information I found the snippet below >> that I think might be relevant to the current XaAES possibilities. What >> about switching to the user context for objc_draw() XaAES calls? Would >> that be possible? Can this be also done for the other say WDIALOG stuff >> callbacks? > > You can't run kernel code in user mode. So you need to cleanly map the > objc_draw() code into the user address space (which is probably not so > easy). And the objc_draw() can't access any kernel data (don't know if > this is necessary). > > > Regards, > Frank > > -- > ATARI FALCON 060 // MILAN 060 > ----------------------------------------- > http://www.cs.uni-magdeburg.de/~fnaumann/ > e-Mail: fnaumann@freemint.de > >