From wookey@wookware.org Thu Sep 24 19:38:20 2009 Received: from dream ([213.165.225.113] helo=dream.aleph1.co.uk) by stoneboat.aleph1.co.uk with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from ) id 1MqtCp-0005CP-L0 for balloon@balloonboard.org; Thu, 24 Sep 2009 19:38:20 +0100 Received: from wookey by dream.aleph1.co.uk with local (Exim 4.69) (envelope-from ) id 1MqtCj-00018l-IV for balloon@balloonboard.org; Thu, 24 Sep 2009 19:38:09 +0100 Date: Thu, 24 Sep 2009 19:38:04 +0100 From: Wookey To: Balloon Message-ID: <20090924183804.GU12991@dream.aleph1.co.uk> Mail-Followup-To: Balloon MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit Organization: Aleph One Ltd User-Agent: Mutt/1.5.18 (2008-05-17) X-SA-Exim-Connect-IP: 213.165.225.113 X-SA-Exim-Mail-From: wookey@wookware.org X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on stoneboat.aleph1.co.uk X-Spam-Level: X-Spam-Status: No, score=-2.6 required=4.5 tests=AWL,BAYES_00 autolearn=no version=3.2.5 X-SA-Exim-Version: 4.2.1 (built Wed, 25 Jun 2008 17:14:11 +0000) X-SA-Exim-Scanned: Yes (on stoneboat.aleph1.co.uk) Subject: [Balloon] Fw: Re: patches for pxafb X-BeenThere: balloon@balloonboard.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: Balloon List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Sep 2009 18:38:21 -0000 This came up in a discussion about pxa framebuffer And it does indeed contain a nice implementation allowing bootloader monitor config. We should clearly steal it. ----- Forwarded message from Mike Rapoport ----- From: Mike Rapoport Date: Thu, 24 Sep 2009 19:48:53 +0300 To: Wookey Subject: Re: patches for pxafb X-Spam-Status: No, score=-4.1 required=4.5 tests=AWL,BAYES_00,SPF_PASS autolearn=no version=3.2.5 > When you say per-machine do you mean per type of machine, or per > device? > > So far as I can see the pxa framebuffer stuff assumes that > every pxa mach type has exactly one display associated with it and > this is built in to the the kernel. This is very tiresome on balloon3, > which so far has had 4 different framebuffer-based displays (QVGA, VGA > LCDs and VGA/SVGA via interface to real monitor) and two > others (accessed over the samosa IO bus), which correspond to 'no frame > buffer'. We currently need different kernel configs and different > kernels to support these which seems deeply crufty, but I'm really not > sure how to go about having displays run or boot-time configurable. > Has anyone thought about how this should be done? Take a look e.g. to arch/arm/mach-pxa/cm-x2xx.c. > Sorry if this is too far off topic for the simple change mooted, but > it seems to me to be part of the same discussion. > > Wookey > -- > Principal hats:  iEndian - Balloonboard - Toby Churchill - Emdebian > http://wookware.org/ > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel > -- Sincerely Yours, Mike. ----- End forwarded message ----- Wookey -- Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian http://wookware.org/