From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Toshiba Tecra 720 (notebook)
Date: Thu, 11 Jan 2001 20:19:44 +0900 [thread overview]
Message-ID: <20010111111951.2D583199DC@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 429 bytes --]
>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
[-- Attachment #2: Type: message/rfc822, Size: 2890 bytes --]
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Toshiba Tecra 720 (notebook)
Date: Tue, 9 Jan 2001 19:22:43 0900
Message-ID: <20010109102301.08D8D19A45@mail.cse.psu.edu>
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 υPD765 FDC, and got a
document on this chip from net
(http://www.htl-steyr.ac.st/_morg/pcinfo/hardware/interrupts/hard0001.html),
and found a command (just 0x10) to check what is the name of this FDC chip
which works only for these NEC's υPD765 families.
Then, I tested this, and got the FDC of this Toshiba Tecra 720 is NEC's
υPD765A or υPD765A-2. This means that we have no means to control
floppy motor rotation speed from this chip, which should be there outside
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
next reply other threads:[~2001-01-11 11:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 11:19 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 10:22 okamoto
2001-01-08 7:01 okamoto
2001-01-05 3:06 okamoto
2001-01-05 3:02 okamoto
2001-01-04 7:40 okamoto
2001-01-04 7:20 okamoto
2001-01-04 5:47 okamoto
2001-01-04 5:31 okamoto
2000-12-30 5:47 okamoto
2000-12-30 2:50 okamoto
2000-12-29 16:22 Russ Cox
2000-12-29 11:36 okamoto
2000-12-29 9:22 okamoto
2000-12-29 8:40 okamoto
2001-01-02 17:45 ` Deztroyer-a1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010111111951.2D583199DC@mail.cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).