From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@transvirtual.com>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] fbdev updates.
Date: Thu, 4 Jul 2002 00:03:54 +0100 [thread overview]
Message-ID: <20020704000354.B4733@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0207011041320.23794-100000@www.transvirtual.com>; from jsimmons@transvirtual.com on Mon, Jul 01, 2002 at 10:48:41AM -0700
On Mon, Jul 01, 2002 at 10:48:41AM -0700, James Simmons wrote:
> Here are the latest updates to the framebuffer layer. Please test it outso
> I can push it as soon as possible to Linus.
The following comments are from a first review of sa1100fb.[ch] changes.
1. It would appear to break sa1100 inverse colourmap stuff. There are LCD
panels out there where it is a rather fundamental requirement to write
the palette with "inverted" colourmap values.
2. I've no idea why you moved "lccr0" and "lccr3" in sa1100fb.h - this
looks like noise to me.
3. I think you replaced "fbi" too many times:
+/* Fake monspecs to fill in infonfo structure */
4. You're also merging in cpufreq changes from my tree in this patch;
however I was going to send these to Linus along with the cpufreq
submission so no problem.
5. I strongly disagree with your apparant decision to make the cpufreq
part of the generic framebuffer core (by apparantly adding the notifier
block to the core fb_info structure). Firstly, you've broken sa1100fb.c
by not including the relevant definition in fb_info (ok, so cpufreq
stuff isn't in Linus' tree yet). Secondly, it isn't something that all
framebuffers require; its only required on SoC devices where the hardware
designers have been stingy. As such, we should NOT penalise the x86
people by adding random useless garbage to structures that they're never
going to use.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
No, I will not fix your computer.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-07-03 23:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 17:48 [PATCH] fbdev updates James Simmons
2002-07-02 13:33 ` Jani Monoses
2002-07-05 2:41 ` James Simmons
2002-07-03 23:03 ` Russell King [this message]
2002-07-05 4:05 ` James Simmons
2002-07-05 8:44 ` Russell King
2002-07-05 8:53 ` Geert Uytterhoeven
2002-07-05 9:09 ` Russell King
2002-07-05 9:39 ` Geert Uytterhoeven
2002-07-05 10:20 ` Russell King
2002-07-05 17:20 ` James Simmons
2002-07-05 17:16 ` James Simmons
2002-07-05 17:58 ` Russell King
2002-07-05 18:21 ` James Simmons
2002-07-05 18:27 ` Russell King
2002-07-05 17:14 ` James Simmons
2002-07-05 17:57 ` Russell King
2002-07-05 18:32 ` James Simmons
2002-07-05 18:39 ` Russell King
2002-07-05 19:00 ` James Simmons
2002-07-05 19:29 ` Ani Joshi
2002-07-05 19:32 ` James Simmons
2002-07-05 19:41 ` Russell King
2002-07-05 19:57 ` James Simmons
2002-07-05 19:53 ` Ani Joshi
2002-07-05 19:55 ` Ani Joshi
2002-07-05 19:58 ` James Simmons
2002-07-05 20:21 ` Ani Joshi
2002-07-05 20:09 ` James Simmons
2002-07-05 20:34 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 5:22 James Simmons
2002-07-08 21:23 James Simmons
2002-06-04 20:05 James Simmons
2002-05-28 18:09 James Simmons
2002-05-22 16:54 James Simmons
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=20020704000354.B4733@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jsimmons@transvirtual.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).