From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:41315) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYGph-0001ft-3F for qemu-devel@nongnu.org; Sun, 19 Jun 2011 08:10:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYGpf-000542-TP for qemu-devel@nongnu.org; Sun, 19 Jun 2011 08:10:29 -0400 Received: from smtp5-g21.free.fr ([212.27.42.5]:40361) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYGpf-00053K-BD for qemu-devel@nongnu.org; Sun, 19 Jun 2011 08:10:27 -0400 Message-ID: <4DFDE725.4060500@reactos.org> Date: Sun, 19 Jun 2011 14:10:13 +0200 From: =?ISO-8859-1?Q?Herv=E9_Poussineau?= MIME-Version: 1.0 References: <67D16361-9E4A-489C-B671-B7D08A50123F@web.de> <1308182564-11748-1-git-send-email-andreas.faerber@web.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [RFC v2 23/23] 40p: Add an IBM 8514/A graphics card List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?ISO-8859-1?Q?Andreas_F=E4rber?= Cc: Blue Swirl , Juan Quintela , =?ISO-8859-1?Q?Herv=E9_Poussinea?= =?ISO-8859-1?Q?u?= , "qemu-devel@nongnu.org Developers" , Roy Tam Andreas F=E4rber a =E9crit : > Am 18.06.2011 um 22:42 schrieb Blue Swirl: >> Please take a look at tcx.c for a 8 bit mode frame buffer with palette >> translation. Also VGA_DIRTY bit handling should be added to this loop >> to speed it up. > > Will look into it. > > I doubt this is causing the long delays though. > * There's an unhandled write to the PCI card's config address 0x4, for=20 > which I have no documentation. I don't have any documentation either for this graphic card :( > * Generally, there are some unhandled writel to 0x680, which look like=20 > IBM progress codes (but I didn't find a manual to decode them -=20 > Herv=E9?), and Port 0x680 is a diagnostic port, related to what appears in the=20 "operator display". 32 bit values are written to this port, and first byte meaning can be=20 found in this document : http://ps-2.kev009.com:8081/rsinfo/Fcodes.htm With that, you can see that first long step is 0x09, ie "Copy CRC=20 verification code to RAM" > * a frequent writeb to 0x690 with value 0x1 or 0x3 (some activity LED=20 > maybe?). > I thought it might be trying to access the missing NCR 53C810 SCSI but=20 > saw no indication of that. The operator display/operator panel also contains 2 LEDs: one for Power=20 On, and the other one for Disk Drive Activity. You might indeed have=20 found the I/O port to control them. Herv=E9