From: Gustavo Junior Alves <alves@coslinux.com.br>
To: Stas Sergeev <stssppnn@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: PIC Problem
Date: Wed, 29 Jan 2003 10:49:22 -0200 [thread overview]
Message-ID: <3E37CDD2.4000908@coslinux.com.br> (raw)
In-Reply-To: <3E373996.8060202@yahoo.com>
The cursor prompt doen't showed on the screen, too. This event occurs
before the keyboard reading (I believe). This may be the source of the
problem???? (Sorry about the stupid question :-) ) If not, you can
advice me about where to start fix this problem?
Gustavo
Stas Sergeev wrote:
> Hello.
>
> Gustavo Junior Alves wrote:
>
>> You remember that problem with keyboard??? (bug 663042
>> <http://sourceforge.net/tracker/index.php?func=detail&aid=663042&group_id=49784&atid=457447>).
>> The problem still occurs on text-mode (on the graphics mode,
>> everything works fine). I have tested on 1.1.4 and 1.1.4.9. You have
>> any ideas?
>
> I have deleted your program a couple
> of years ago, but IIRC it was masking
> the keyboard IRQ and was reading the
> port60 for keypresses - extremely dumb
> way of dealing with keyboard and have
> nothing to do with PIC btw.
> AFAIK the problem with terminal mode is
> that we can't detect the release events,
> so the release event is passed to the
> program immediately after the press
> event, and if the program uses a polling
> technique, then it will miss the press
> event as it lasts for the very short
> period.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2003-01-29 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 2:16 PIC Problem Stas Sergeev
2003-01-29 12:49 ` Gustavo Junior Alves [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-04 9:05 Stas Sergeev
2003-01-01 2:24 ` Gustavo Junior Alves
2003-01-06 11:04 ` Gustavo Junior Alves
2003-01-28 16:27 ` Gustavo Junior Alves
2003-01-28 17:10 ` Bart Oldeman
2003-01-02 19:29 Gustavo Junior Alves
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=3E37CDD2.4000908@coslinux.com.br \
--to=alves@coslinux.com.br \
--cc=linux-msdos@vger.kernel.org \
--cc=stssppnn@yahoo.com \
/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