From: Wolfgang Grandegger <wg@grandegger.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [RFC] Splash image
Date: Thu, 19 Jul 2007 22:30:51 +0200 [thread overview]
Message-ID: <469FC9FB.4020302@grandegger.com> (raw)
In-Reply-To: <008901c7ca10$f1921a40$d4b64ec0$@com>
Joey Oravec wrote:
> "Wolfgang Grandegger" <wg@grandegger.com> wrote in message
> news:<469F334F.6040003@grandegger.com>...
>>> In order to adapt pxafb support to "drivers/cfb_console.c" I think I
>>> should move cpu/pxa/pxafb.c to drivers/pxafb.c adapting the internal
>>> functions to use video_hw_init() and video_set_lut(). Is that right?
>> I think so and drivers is also the correct place for pxafb.c.
>
> That doesn't seem like a great move. The drivers folder is just a collection
> of garbage which is board specific anyway right now.
Well, yes, that's a to-do for u-boot-v2. In another mail to the list I
already suggested _not_ to waste too much time with the old video
drivers but concentrate the effort on a unified driver for u-boot-v2.
> Where may I download your patches? I have not seen your changes yet, and I
> would like to see if this is completely PXA specific or if any of that is
> reusable for AT91, MPC, or other hardware.
I'm going to post it next week. The dynamic display configuration is
implemented for the MPC823, other stuff is useful for PXA as well, like
splash image rotation.
> It makes sense to have a framebuffer.c in drivers which is common to every
> chip, every framebuffer, and everything that you could ever want to program.
> It also makes sense to have some support code in common that opens BMP
> files, draws something upon the frame buffer, etc. Finally it makes sense to
> have CPU specific code that initializes the registers, DMA, and everything
> for the specific chip.
Yes, we have something like that already, e.g. driver/cfb_console.c.
Unfortunately, it does not support monochrome displays. Furthermore
there is "common/lcd.c" mainly for the FB of the MPC823 and PXA
supporting monochrome and 8-bit with color-map display.
> I will take a look at the code but I'm a little worried based on what I've
> read so far. This sounds like the changes may be very specific to one CPU or
> one board and not a general driver framework.
The patch will add more features to "common/lcd.c" but it will
definitely not improve the general driver framework.
Wolfgang.
next parent reply other threads:[~2007-07-19 20:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <008901c7ca10$f1921a40$d4b64ec0$@com>
2007-07-19 20:30 ` Wolfgang Grandegger [this message]
2007-07-18 8:30 [U-Boot-Users] [RFC] Splash image Rodolfo Giometti
2007-07-18 13:40 ` Joey Oravec
2007-07-18 13:58 ` Rodolfo Giometti
2007-07-18 14:31 ` Jerry Van Baren
2007-07-18 15:32 ` Rodolfo Giometti
2007-07-18 14:47 ` Wolfgang Grandegger
2007-07-18 15:37 ` Rodolfo Giometti
2007-07-18 16:03 ` Wolfgang Grandegger
2007-07-18 16:01 ` Rodolfo Giometti
2007-07-18 16:17 ` Wolfgang Grandegger
2007-07-19 8:36 ` Rodolfo Giometti
2007-07-19 9:47 ` Wolfgang Grandegger
2007-07-19 9:52 ` Rodolfo Giometti
2007-07-19 14:18 ` Rodolfo Giometti
2007-07-19 14:41 ` Wolfgang Grandegger
2007-07-19 14:40 ` Rodolfo Giometti
2007-07-19 7:09 ` Matthias Fuchs
2007-07-19 8:19 ` Wolfgang Grandegger
2007-07-19 8:33 ` Rodolfo Giometti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=469FC9FB.4020302@grandegger.com \
--to=wg@grandegger.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox