From owner-freebsd-arch@FreeBSD.ORG  Sat Oct 29 03:52:23 2005
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: freebsd-arch@freebsd.org
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 53ACE16A41F;
	Sat, 29 Oct 2005 03:52:23 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E38C643D45;
	Sat, 29 Oct 2005 03:52:22 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9T3ojhN066202;
	Fri, 28 Oct 2005 21:50:45 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Fri, 28 Oct 2005 21:50:49 -0600 (MDT)
Message-Id: <20051028.215049.102576958.imp@bsdimp.com>
To: babkin@users.sourceforge.net, babkin@verizon.net
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <4362B611.B4A12AF8@verizon.net>
References: <12768156.1130520253107.JavaMail.root@vms073.mailsrvcs.net>
	<200510281435.41700.jhb@freebsd.org>
	<4362B611.B4A12AF8@verizon.net>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Fri, 28 Oct 2005 21:50:50 -0600 (MDT)
Cc: gbergling@0xfce3.net, phk@phk.freebsd.dk, freebsd-arch@freebsd.org
Subject: Re: wscons for FreeBSD?
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Oct 2005 03:52:23 -0000

In message: <4362B611.B4A12AF8@verizon.net>
            Sergey Babkin <babkin@verizon.net> writes:
: John Baldwin wrote:
: > 
: > On Friday 28 October 2005 01:24 pm, Sergey Babkin wrote:
: > > >From: John Baldwin <jhb@freebsd.org>
: > > >
: 
: > > * When entering panic/debugger mode the console
: > >   should reset its video mode to the one where
: > >   the panic information is visible.
: > 
: > I think this might be kind of hard since you really don't know what X has done
: > to the hardware unless you make X talk to the console driver to do
: > everything.
: 
: Can you re-initialize the device from scratch? My knowledge
: about the video hardware dates to SVGA times and even that
: is not too deep.
: 
: Maybe provide a basic SVGA re-initialization routine on x86 and have
: an interface for the third-party in-kernel drivers that
: would contain the re-initialization routine.

When this has come up in the past, those in the know say that it takes
card specific registers and knowledge to reset these cards' video
modes.

Warner