From owner-freebsd-doc@FreeBSD.ORG Wed Jul 4 02:34:08 2012 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C256106564A for ; Wed, 4 Jul 2012 02:34:08 +0000 (UTC) (envelope-from bjk@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 254978FC08; Wed, 4 Jul 2012 02:34:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q642Y8Xa057361; Wed, 4 Jul 2012 02:34:08 GMT (envelope-from bjk@freebsd.org) Received: from localhost (bjk@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) with ESMTP id q642Y7f7057358; Wed, 4 Jul 2012 02:34:07 GMT (envelope-from bjk@freebsd.org) X-Authentication-Warning: freefall.freebsd.org: bjk owned process doing -bs Date: Wed, 4 Jul 2012 02:34:07 +0000 (UTC) From: Benjamin Kaduk To: Warren Block In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: doc@freebsd.org Subject: Re: Handbook update: HorizSync and VertRefresh X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 02:34:08 -0000 On Mon, 2 Jul 2012, Warren Block wrote: > The X11 configuration chapter of the Handbook has some very old > information which is confusing users. Manually setting HorizSync and > VertRefresh has been mostly useless for many years, and should be > deemphasized. > > This patch does that. Instead of saying the sync frequencies must > always be entered, it adds some information about autodetection and > points out that almost all monitors support it. Also added is a note > not to guess about sync frequencies. On the CRT monitors where it > matters, it can matter a lot. Some of those monitors might still be > functional. One does hear the occasional tale of a CRT which exploded when the wrong frequencies were configured ... it might be worth mentioning that guessing values could lead to hardware damage. > > Feedback welcome. If there aren't any loud screams of outrage, squawks > of offense, or mere bacaws of disgust, I'll commit it in a couple of > days. It seems basically reasonable. -Ben