From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] video: add PXA3xx accelerator ID [v2]
Date: Sat, 12 Sep 2009 00:12:52 +0800 [thread overview]
Message-ID: <f17812d70909110912q41c45dcfl8410e3fb51ec7e9c@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909101530120.4458@axis700.grange>
> Ok, now remove 'cpu_is_pxa3xx() && ' above and you should be good to go:-)
> What if tomorrow pxa4xx comes (ok, Eric will disagree, but wtill:-))
It is not likely to be pxa4xx, (chinese people don't like '4', and there are
a lot chinese in Marvell, Shhh..... don't let them know I said this ;-)
Still, I guess having a cpu_is_pxa3xx() should be OK here.
>
>> ? ? ? fbi->backlight_power = inf->pxafb_backlight_power;
>> ? ? ? fbi->lcd_power = inf->pxafb_lcd_power;
>>
>> diff --git a/include/linux/fb.h b/include/linux/fb.h
>> index f847df9..a34bdf5 100644
>> --- a/include/linux/fb.h
>> +++ b/include/linux/fb.h
>> @@ -133,6 +133,7 @@ struct dentry;
>> ?#define FB_ACCEL_NEOMAGIC_NM2230 96 ?/* NeoMagic NM2230 ? ? ? ? ? ? ?*/
>> ?#define FB_ACCEL_NEOMAGIC_NM2360 97 ?/* NeoMagic NM2360 ? ? ? ? ? ? ?*/
>> ?#define FB_ACCEL_NEOMAGIC_NM2380 98 ?/* NeoMagic NM2380 ? ? ? ? ? ? ?*/
>> +#define FB_ACCEL_PXA3XX ? ? ? ? ? ? ? 99 ? ? /* PXA3xx ? ? ? ? ? ? ? ? ? ? ? */
>>
>> ?#define FB_ACCEL_SAVAGE4 ? ? ? ?0x80 /* S3 Savage4 ? ? ? ? ? ? ? ? ? */
>> ?#define FB_ACCEL_SAVAGE3D ? ? ? 0x81 /* S3 Savage3D ? ? ? ? ? ? ? ? ?*/
>> --
>> 1.6.3.3
>>
>
> Thanks
> Guennadi
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
prev parent reply other threads:[~2009-09-11 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 13:26 [PATCH] video: add PXA3xx accelerator ID [v2] Daniel Mack
2009-09-10 13:31 ` Guennadi Liakhovetski
2009-09-10 13:33 ` Daniel Mack
2009-09-11 15:20 ` Daniel Mack
2009-09-11 16:12 ` Eric Miao [this message]
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=f17812d70909110912q41c45dcfl8410e3fb51ec7e9c@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).