From: Marc Reilly <marc@cpdesign.com.au>
To: barebox@lists.infradead.org
Subject: Re: [PATCH 3/4] ARM i.MX28 tx28: use a fixed framebuffer address
Date: Tue, 18 Jan 2011 09:49:35 +1100 [thread overview]
Message-ID: <201101180949.35371.marc@cpdesign.com.au> (raw)
In-Reply-To: <201101171159.31154.jbe@pengutronix.de>
> > static struct imx_fb_videomode imxfb_mode = {
> >
> > .mode_list = tx28evk_vmodes,
> > .mode_cnt = ARRAY_SIZE(tx28evk_vmodes),
> > .dotclk_delay = 0, /* no adaption required */
> > .ld_intf_width = STMLCDIF_24BIT, /* full 24 bit */
> >
> > + .fixed_screen = (void *)(0x40000000 + SZ_128M - MAX_FB_SIZE),
> > + .fixed_screen_size = MAX_FB_SIZE,
> >
> > };
>
> Question only: Any idea how we could make this setup (base address and size
> of the fixed screen) a runtime feature? This would be a nice feature like
> most modern BIOS also have: Make the size of the video memory shared with
> the CPU selectable at runtime.
>
Purely out of interest, what is the advantage/necessity for having the frame
buffer at a fixed address?
Cheers
Marc
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-01-17 22:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 10:22 i.MX28 patches v2 Sascha Hauer
2011-01-17 10:22 ` [PATCH 1/4] video stm/mx2x: simplify memory allocation Sascha Hauer
2011-01-17 10:22 ` [PATCH 2/4] video stm/mx2x: allow to pass in fb memory from platform data Sascha Hauer
2011-01-17 17:56 ` [PATCH 2/4 v2] " Sascha Hauer
2011-01-17 10:22 ` [PATCH 3/4] ARM i.MX28 tx28: use a fixed framebuffer address Sascha Hauer
2011-01-17 10:59 ` Juergen Beisert
2011-01-17 22:49 ` Marc Reilly [this message]
2011-01-18 7:48 ` Peter Korsgaard
2011-01-18 9:41 ` Juergen Beisert
2011-01-17 10:22 ` [PATCH 4/4] ARM i.MX28 tx28 defconfig: enable MMU Sascha Hauer
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=201101180949.35371.marc@cpdesign.com.au \
--to=marc@cpdesign.com.au \
--cc=barebox@lists.infradead.org \
/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