From owner-freebsd-arch@FreeBSD.ORG Mon Mar 3 17:46:48 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A837D496 for ; Mon, 3 Mar 2014 17:46:48 +0000 (UTC) Received: from mail-pb0-f41.google.com (mail-pb0-f41.google.com [209.85.160.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7AD5F391 for ; Mon, 3 Mar 2014 17:46:48 +0000 (UTC) Received: by mail-pb0-f41.google.com with SMTP id jt11so4069338pbb.0 for ; Mon, 03 Mar 2014 09:46:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=Hy8V9qo4KWoMoeSukhVFznsVGBuWqjJY+3fZUV55zvQ=; b=MsbM0ylhI9xBD6Ed7HdetMUy6TiZRNiqCb1R6rCR212vZl/zLc3izeuGYDpUiQdOym pG1o0kbvl00luHrKhs37xVuYRVZQZESl7OxFMy98zKtVbY9NatJzwvg4StlVdOdUSk64 DPByHuguhNaT+IQAhMO9g24yBJ9nAhdqO6u8RjnrbR1MOPHPa1K8FVVpaj0KyRVB8OEL X9hUYUQbq4LgeaB+Vx9uW5Dt/R6G0DDIUQfBci9fUNzPSenAbu/0ZTiNSEmdLrD6TKJF Brv8WYoX4vihbMVtjS3PPyWc2UuUHiDT1vazVZPYlcwWd+Q0rgUUxSwuv5+V/bHKzZYY mV0w== X-Gm-Message-State: ALoCoQlQnV/THyXHEiabTxvq2DBZV5I3+7QaXHZfFaO5zJ4aZ3pt8mFdxZkHt+E79te1mNXYNM9R X-Received: by 10.68.232.134 with SMTP id to6mr4961976pbc.107.1393868802363; Mon, 03 Mar 2014 09:46:42 -0800 (PST) Received: from [10.64.27.32] (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id yx3sm11893891pbb.6.2014.03.03.09.46.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Mar 2014 09:46:41 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: newcons fb driver From: Warner Losh In-Reply-To: Date: Mon, 3 Mar 2014 10:46:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <42130.1393829535@critter.freebsd.dk> <5314B2A2.3060100@pix.net> To: Justin Hibbits X-Mailer: Apple Mail (2.1874) Cc: freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Mar 2014 17:46:48 -0000 On Mar 3, 2014, at 10:44 AM, Justin Hibbits = wrote: > On Mon, Mar 3, 2014 at 8:49 AM, Kurt Lidl wrote: >>> In message >> mail.gmail.com> >>>=20 >>> , Adrian Chadd writes: >>>=20 >>>> .. i'm pretty sure there was a reason for why it's done in byte = sizes. >>>> Maybe speak to phk? >>>=20 >>>=20 >>> Buggy video hardware, which does not do larger writes correctly, >>> the most recent one being an Intel Laptop, but I can't remember = which. >>>=20 >>> At the very least, byte writes needs to be a boot-time option. >>=20 >>=20 >> Intel Atom boards, as I recall: >>=20 >> http://freshbsd.org/commit/freebsd/r237203 >>=20 >> -Kurt >=20 > All great knowledge, but really only answers half of what I'm looking > for (always good to know potential pitfalls). Assuming a > tunable/sysctl is added, what's the best way to optimize from my > original post? Use a backing buffer (potentially with a tunable to > not)? Or assume we don't support background images, and write the > background color in the masked pixels? Most of the issues are with the CHARACTER buffer, not the actual frame = (pixel) buffer=85 Warner