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 <
mike.rapoport@gmail.com> -----
From: Mike Rapoport <mike.rapoport@gmail.com>
Date: Thu, 24 Sep 2009 19:48:53 +0300
To: Wookey <wookey@wookware.org>
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/