ORIGEN board is fitted with 7 LCD panel HV070WSA. The pixel
resolution of the LCD panel is 1024x600.
Also power domain device for LCD0 is registered.
Signed-off-by: Tushar Behera tushar.beh...@linaro.org
---
Changes for V4:
* Added gpio_free() call
* Removed .refresh value as it
Hi,
I am using the ALIP filesystem with my own kernel and kernel modules (2.6.35).
The startup seems to encounter 3 errors after which it does not proceed any
further. If I am moving outside of an area you can help with I understand. If
you can give me a tip on what could possibly be happening
Dear Tushar Behera,
In message 1316076867-2138-1-git-send-email-tushar.beh...@linaro.org you
wrote:
ORIGEN board is fitted with 7 LCD panel HV070WSA. The pixel
resolution of the LCD panel is 1024x600.
...
+static struct s3c_fb_pd_win origen_fb_win0 = {
+ .win_mode = {
+
On Thu, Sep 15, 2011 at 10:05:59AM +0100, Frederik Lotter wrote:
The startup seems to encounter 3 errors after which it does not
proceed any further. If I am moving outside of an area you can help
with I understand. If you can give me a tip on what could possibly be
happening here that would
Dear Wolfgang Denk,
On Thursday 15 September 2011 02:44 PM, Wolfgang Denk wrote:
Dear Tushar Behera,
In message1316076867-2138-1-git-send-email-tushar.beh...@linaro.org you
wrote:
ORIGEN board is fitted with 7 LCD panel HV070WSA. The pixel
resolution of the LCD panel is 1024x600.
...
Hi,
I am the author of OMAP display driver, and while developing it I've
often felt that there's something missing in Linux's display area. I've
been planning to write a post about this for a few years already, but I
never got to it. So here goes at last!
---
First I want to (try to) describe
Since we have had over 300 views of NEON optimization on ask.linaro.org, it
looks like there is enough interest in continuing the NEON Forum face2face
meetings at LC Orlando.
I am collecting topics for discussion and wanted to extend an invite to the
broader team, to see if anyone wanted to
Hello Michael,
On Tue, 06 Sep 2011 08:35:57 +1200
Michael Hudson-Doyle michael.hud...@canonical.com wrote:
On Mon, 5 Sep 2011 16:18:34 +0300, Paul Sokolovsky
paul.sokolov...@linaro.org wrote:
Hello,
We're running Jenkins EC2 plugin v 1.11 on android-build.linaro.org,
which is 2
Hi Tomi,
On Thu, Sep 15, 2011 at 9:07 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
Hi,
I am the author of OMAP display driver, and while developing it I've
often felt that there's something missing in Linux's display area. I've
been planning to write a post about this for a few years
On Thu, 15 Sep 2011 15:07:05 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
This was a very rough and quite short proposal, but I'm happy to improve
and extend it if it's not totally shot down.
Jesse Barnes has put together a proposal much like this to work within
the existing DRM
On Thu, 2011-09-15 at 09:59 -0500, Keith Packard wrote:
On Thu, 15 Sep 2011 15:07:05 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
This was a very rough and quite short proposal, but I'm happy to improve
and extend it if it's not totally shot down.
Jesse Barnes has put together a
On Thu, 15 Sep 2011 10:50:32 -0500
Keith Packard kei...@keithp.com wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the plan is to make DRM the core Linux display framework, upon
is and we could use it. Such attitude is not helpful and as I don't see any
serious intention of the DRM guys to cooperate I think those subsystems are
more
likely to diverge. At least I'll never accept any change to the fb
infrastructure that requires DRM.
There are aspects of the fb code
On Thu, 2011-09-15 at 10:50 -0500, Keith Packard wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the plan is to make DRM the core Linux display framework, upon which
everything
Once the interrupt issue is resolved I might suggest sampling cpu-cycles as a
workaround to real-time sampling granularity, except that there apparently
is an issue with reliably getting interrupts from the PMU. Does anyone know
if this is still a problem in the A9 (I've only seen it
On Thu, Sep 15, 2011 at 12:21 PM, Tomi Valkeinen tomi.valkei...@ti.com wrote:
On Thu, 2011-09-15 at 10:50 -0500, Keith Packard wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the
What is your problem with discontigous framebuffers? (I assume discontigous
refers to the pages the framebuffer is composed of)
Sounds to me like you should implement your own fb_mmap and either map it
contigous to screen_base or implement your own fb_read/write.
In theory you could even have
As you have DRM now and as I'm not interested in wayland I won't discuss this,
but I guess it might be a good start for Geert's question what would be needed
to use it on dumb framebuffers.
GMA500 is basically a 2D or dumb frame buffer setup but with a lot of
rather complicated output and
I'm writing up some notes on building Android from scratch and
replacing the kernel in an Android build from one built locally, and I
realized that's it a bit of a chore to extract the kernel config that
got used. I thought, it may make sense to provide an way in
android-build to control what gets
On Thu, 15 Sep 2011 15:08:26 -0500, Zach Pfeffer zach.pfef...@linaro.org
wrote:
I'm writing up some notes on building Android from scratch and
replacing the kernel in an Android build from one built locally, and I
realized that's it a bit of a chore to extract the kernel config that
got used.
On 15 September 2011 15:58, James Westby james.wes...@linaro.org wrote:
On Thu, 15 Sep 2011 15:08:26 -0500, Zach Pfeffer zach.pfef...@linaro.org
wrote:
I'm writing up some notes on building Android from scratch and
replacing the kernel in an Android build from one built locally, and I
Okay, I see your problem. It's a bit strange you don't have acceleration. I
The hardware has 3D acceleration but not open so we can't support it.
There is no 2D acceleration - which seems to be increasingly common.
At some point I'll add hardware scrolling however by using the GTT to
implemnent
On 09/15/2011 03:50 PM, Keith Packard wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the plan is to make DRM the core Linux display framework, upon which
everything else is built,
Hi Alan,
On 09/15/2011 05:18 PM, Alan Cox wrote:
is and we could use it. Such attitude is not helpful and as I don't see any
serious intention of the DRM guys to cooperate I think those subsystems are
more
likely to diverge. At least I'll never accept any change to the fb
infrastructure
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the plan is to make DRM the core Linux display framework, upon which
everything else is built, and fb and v4l2 are changed to use DRM.
I'd
On Thu, Sep 15, 2011 at 1:12 PM, Florian Tobias Schandinat
florianschandi...@gmx.de wrote:
On 09/15/2011 03:50 PM, Keith Packard wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it doesn't help fb or v4l2 drivers. Except if
the
On Thu, Sep 15, 2011 at 19:52, Alex Deucher alexdeuc...@gmail.com wrote:
While the DRM has historically targeted 3D acceleration, that is not a
requirement to use the DRM KMS modesetting API. The current fb API
has no concept of display controllers or connectors or overlays, etc.
To match it
On 09/15/2011 05:52 PM, Alex Deucher wrote:
On Thu, Sep 15, 2011 at 1:12 PM, Florian Tobias Schandinat
florianschandi...@gmx.de wrote:
On 09/15/2011 03:50 PM, Keith Packard wrote:
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen tomi.valkei...@ti.com
wrote:
1) It's part of DRM, so it
On 09/15/2011 06:58 PM, Alan Cox wrote:
Well, I rather think that the fb API is more user centric to allow every
program
to use it directly in contrast to the KMS/DRM API which aims to support every
feature the hardware has. For this the fb API should not change much, but I
understand some
On Thu, 15 Sep 2011 17:12:43 +, Florian Tobias Schandinat
florianschandi...@gmx.de wrote:
Interesting that this comes from the people that pushed the latest mode
setting
code into the kernel. But I don't think that this will happen, the exposed
user
interfaces will be around for
Sending from a mobile, pardon my terseness. ~ C.
On Sep 15, 2011 1:05 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, Sep 15, 2011 at 1:56 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Thu, Sep 15, 2011 at 19:52, Alex Deucher alexdeuc...@gmail.com
wrote:
While the DRM has
Wasn't there a driver for qemu cirrus hardware?
Sending from a mobile, pardon my terseness. ~ C.
On Sep 15, 2011 1:05 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, Sep 15, 2011 at 1:56 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Thu, Sep 15, 2011 at 19:52, Alex Deucher
On 09/15/2011 07:05 PM, Alan Cox wrote:
What is your problem with discontigous framebuffers? (I assume discontigous
refers to the pages the framebuffer is composed of)
Sounds to me like you should implement your own fb_mmap and either map it
contigous to screen_base or implement your own
On Thu, Sep 15, 2011 at 3:18 PM, Florian Tobias Schandinat
florianschandi...@gmx.de wrote:
On 09/15/2011 06:58 PM, Alan Cox wrote:
Well, I rather think that the fb API is more user centric to allow every
program
to use it directly in contrast to the KMS/DRM API which aims to support
every
I get these questions a lot so I wrote some blog posts with the exact
steps I used.
http://www.linaro.org/linaro-blog/2011/09/15/switching-out-a-pre-built-android-images-kernel/
http://www.linaro.org/linaro-blog/2011/09/15/%EF%BB%BFbuilding-a-linaro-android-build-from-source/
Enjoy!
--
Zach
35 matches
Mail list logo
