From fnaumann@mail.cs.uni-magdeburg.de Sat Jul 31 20:54:55 2004 Subject: [MiNT] [Fwd: Re: [Emutos-devel] FYI [Fwd: Re: Keyboard input fails with 1.16.1]] From: Petr Stehlik To: MiNT Mailing List Content-Type: text/plain; charset=ISO-8859-2 Message-Id: <1091299304.2106.2.camel@joy.home> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sat, 31 Jul 2004 20:41:44 +0200 X-MIME-Autoconverted: from 8bit to quoted-printable by ns1.avonet.cz id UAA03421 Delivered-To: mint@fishpool.com Delivered-To: mint@lists.fishpool.fi X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: joy@sophics.cz Precedence: bulk List-help: List-unsubscribe: List-ID: X-List-ID: X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel X-Milter: ClamAV 0.70/0.70kjel X-Milter: milter-regex 1.5jel Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i6VIseSg002202 -----Přeposlaná zpráva----- From: Laurent Vogel To: emutos-devel@lists.sourceforge.net Subject: Re: [Emutos-devel] FYI [Fwd: Re: [MiNT] Keyboard input fails with 1.16.1] Date: Thu, 29 Jul 2004 21:07:02 +0200 Petr Stehlik forwarded what Konrad Kokoszkiewicz wrote: > > So, unless I overlook something, it is to be concluded, that EmuTOS, > eventhough it claims to be TOS version 2.06, lacks the TOS 2.06 BIOS > functionality in this area, i.e. the kbdvec vector, which is used by > FreeMiNT to intercept keyboard scancodes. Emutos implements the kbdvecs structure as documented in the compendium. (see bios/aciavecs.[Sh]). It even uses it internally. However the implementation of the interrupt vectors themselves, although compliant to the documentation, is not strictly identical to the TOS implementation (for instance, the TOS copies IKBD packets of different types in different buffers whereas the current EmuTOS implementation * uses a common buffer, IIRC). Now, I would be glad to know what use the MiNT guys make of this kbdvecs structure... Laurent