From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
David Vrabel <dvrabel@arcom.com>
Subject: Re: [patch] (Preliminary) Geode framebuffer driver.
Date: Tue, 15 Feb 2005 21:38:24 +0800 [thread overview]
Message-ID: <200502152138.24361.adaplas@hotpop.com> (raw)
In-Reply-To: <4211D969.6070106@arcom.com>
On Tuesday 15 February 2005 19:13, David Vrabel wrote:
> Antonino A. Daplas wrote:
> > On Friday 11 February 2005 19:11, David Vrabel wrote:
> >>Attached is a patch (against 2.6.10) for a framebuffer driver for the
> >>Geode family of processors. It does not use AMD's horrible Durango API.
> >> It is, however, rather feature incomplete at the moment.
> >>
> >> * Only Geode GX1 (with CS5530 companion chip) is supported.
> >> * Tested resolutions: 640x480 to 1280x1024.
> >> * Supported bit depths: 8 bit palette, 16 bit RGB 5-6-5.
> >> * CRT output only.
> >> * No accelerated features.
> >> * Compression is not enabled.
> >>
> >>Could this patch be considered for inclusion, please?
> >
> > Yes.
> >
> > However, I would prefer that instead of:
> >
> > struct geodefb_info {
> > struct fb_info fb;
> > ...
> >
> > use struct fb_info.par for all driver private data and use
> > framebuffer_release()/framebuffer_alloc() to de/allocate the fb_info
> > structure.
>
> Done this now. An updated patch is attached.
>
> This also includes a number of other changes:
>
> - now works when built into the kernel
> - flat panel support (panel=<x>x<y> option). (Only one 640x480 panel
> has been tested though.)
> - blank function for display blanking/powersaving.
> - crt=<n> option to enable/disable the CRT output.
>
> David Vrabel
A few minor comments:
+ /* Clear the frame buffer of garbage. */
+ memset(info->screen_base, 0, info->fix.smem_len);
Is the above really necessary? And if it is, memset_io is preferred.
+ info->screen_base = (unsigned char *)ioremap(info->fix.smem_start, info->fix.smem_len);
You also do not need the (unsigned char *) part. (sparse will complain.)
No need to resend the patch, just let me know what changes you want, if any.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-15 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 11:11 [patch] (Preliminary) Geode framebuffer driver David Vrabel
2005-02-11 20:39 ` Antonino A. Daplas
2005-02-15 11:13 ` David Vrabel
2005-02-15 13:38 ` Antonino A. Daplas [this message]
2005-02-15 14:15 ` David Vrabel
2005-02-15 14:34 ` Antonino A. Daplas
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=200502152138.24361.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=dvrabel@arcom.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.