[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: some console code checked in

From: Jeroen Dekkers
Subject: Re: some console code checked in
Date: Mon, 18 Mar 2002 16:51:37 +0100
User-agent: Mutt/1.3.27i

On Mon, Mar 18, 2002 at 01:29:35PM +0100, Marcus Brinkmann wrote:
> On Mon, Mar 18, 2002 at 03:12:54AM -0500, Roland McGrath wrote:
> > I don't think anything else uses those particular io ports (0x61 turns the
> > speaker on, 0x48 controls the timer that drives the tone frequency), so
> > console could just diddle them directly as it does for VGA (though there is
> > the timing question--it would suck to have your speaker keep beeping while
> > something gets paged in before console runs again to turn it off).  
> Yes, this is a serious problem.  It is also not easy to solve this in the
> kernel. What you can get easily is a beep that blocks the system, but I am
> not sure how hard it is to get a non-blocking beep at the kernel level
> (seems to require some interrupt stuff to switch it off at the right time?).

What's wrong with a high priority thread doing the beep which blocks for a
specific amount of time during the beep?

Jeroen Dekkers
Jabber supporter - http://www.jabber.org Jabber ID: jdekkers@jabber.org
Debian GNU supporter - http://www.debian.org http://www.gnu.org
IRC: jeroen@openprojects

Attachment: pgpxPeojRTzin.pgp
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]