From: Daniel Mack <daniel@caiaq.de>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Sven Neumann <s.neumann@raumfeld.com>,
linux-fbdev-devel@lists.sourceforge.net,
Eric Miao <eric.y.miao@gmail.com>,
Dennis Oliver Kropp <dok@directfb.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] video: add PXA3xx accelerator ID [v2]
Date: Fri, 11 Sep 2009 17:20:19 +0200 [thread overview]
Message-ID: <20090911152019.GZ18340@buzzloop.caiaq.de> (raw)
In-Reply-To: <20090910133327.GA9410@buzzloop.caiaq.de>
On Thu, Sep 10, 2009 at 03:33:27PM +0200, Daniel Mack wrote:
> On Thu, Sep 10, 2009 at 03:31:34PM +0200, Guennadi Liakhovetski wrote:
> > > + if (cpu_is_pxa3xx() && inf->acceleration_enabled)
> > > + fbi->fb.fix.accel = FB_ACCEL_PXA3XX;
> > > +
> >
> > 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:-))
>
> Don't know. I left it in there intentionally, but I'm fine to remove it.
> Or Eric does it when applying ;) Eric?
What I was considering are cases where a kernel binary that works on
both PXA3xx and other PXAs shares the same pxafb_mach_info struct across
different board support code. The accel flag would then be set for wrong
platforms.
But this might be academic, that's why I don't have a strong opinion on
that :)
Daniel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
next prev parent reply other threads:[~2009-09-11 15:20 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 [this message]
2009-09-11 16:12 ` Eric Miao
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=20090911152019.GZ18340@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=dok@directfb.org \
--cc=eric.y.miao@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=s.neumann@raumfeld.com \
/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).