From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Toshiba Tecra 720 (notebook) From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-uplkcffcajbnuzqfqxdczsbzty" Message-Id: <20010111111951.2D583199DC@mail.cse.psu.edu> Date: Thu, 11 Jan 2001 20:19:44 +0900 Topicbox-Message-UUID: 4baeeb0c-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-uplkcffcajbnuzqfqxdczsbzty Content-Disposition: inline Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit >In fact, commands are sent safely to FDC, and I get right results other >than floppyxfer() which uses DMA transfer. When I'm reading japanese documentation on υPD765 FDC chip, I found this chip requires response from the CPU within a relatively short time period, such that 14υS. If there is no such response from the CPU, it goes to overrun error. Does the Plan 9 DMA mechanism can satisfy this demand? Kenji --upas-uplkcffcajbnuzqfqxdczsbzty Content-Type: message/rfc822 Content-Disposition: inline Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by granite.cias.osakafu-u.ac.jp; Tue Jan 9 19:13:28 JST 2001 Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2]) by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id TAA12705; Tue, 9 Jan 2001 19:24:07 +0900 Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6]) by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-00112717) with ESMTP id TAA21651; Tue, 9 Jan 2001 19:24:33 +0900 (JST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.20.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 72E5E19A4D; Tue, 9 Jan 2001 05:24:10 -0500 (EST) Received: from granite.cias.osakafu-u.ac.jp (granite.cias.osakafu-u.ac.jp [157.16.91.52]) by mail.cse.psu.edu (CSE Mail Server) with SMTP id 08D8D19A45 for <9fans@cse.psu.edu>; Tue, 9 Jan 2001 05:23:01 -0500 (EST) To: 9fans@cse.psu.edu Subject: Re: [9fans] Toshiba Tecra 720 (notebook) From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Message-Id: <20010109102301.08D8D19A45@mail.cse.psu.edu> Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Tue, 9 Jan 2001 19:22:43 0900 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by granite.cias.osakafu-u.ac.jp id TAA12705 nclude: /mail/fs/mbox/55/raw Well,... I'm still here (too much anxious to leave from here). I suspected this Toshiba machine may use NEC's =CF=85PD765 FDC, and got a document on this chip from net=20 (http://www.htl-steyr.ac.st/_morg/pcinfo/hardware/interrupts/hard0001.htm= l), and found a command (just 0x10) to check what is the name of this FDC ch= ip=20 which works only for these NEC's =CF=85PD765 families. Then, I tested this, and got the FDC of this Toshiba Tecra 720 is NEC's=20 =CF=85PD765A or =CF=85PD765A-2. This means that we have no means to cont= rol=20 floppy motor rotation speed from this chip, which should be there outside= =20 the chip. However, I may not be facing this problem now(I'm not sure). The document says this FDC chip is not different from the coded one in /sys/src/9/pc/devfloppy.c where I cannot find any problem sofar. In fact, commands are sent safely to FDC, and I get right results other than floppyxfer() which uses DMA transfer. Are there any recommendation to check if this is just the problem whichi I'm facing. Anyway, the document says "INT 6 sets bit 7 of BIOS Data Area location 40= :3E which can be polled for completion status." Is this also right for Plan = 9 kernel? Kenji --upas-uplkcffcajbnuzqfqxdczsbzty--