On Thu, 2011-09-15 at 19:55 -0500, Keith Packard wrote:
> On Thu, 15 Sep 2011 20:21:15 +0300, Tomi Valkeinen
> wrote:
>
> > 2) panel drivers, handles panel specific things. Each panel may support
> > custom commands and features, for which we need a dedicated driver. And
> > this driver is not p
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 Pfe
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 ow
On Thu, Sep 15, 2011 at 3:18 PM, Florian Tobias Schandinat
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
>>> feature t
On Thu, 15 Sep 2011 17:12:43 +, Florian Tobias Schandinat
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 decades and the infrastru
Sending from a mobile, pardon my terseness. ~ C.
On Sep 15, 2011 1:05 PM, "Alex Deucher" wrote:
> On Thu, Sep 15, 2011 at 1:56 PM, Geert Uytterhoeven
> wrote:
>> On Thu, Sep 15, 2011 at 19:52, Alex Deucher
wrote:
>>> While the DRM has historically targeted 3D acceleration, that is not a
>>> requ
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" wrote:
> On Thu, Sep 15, 2011 at 1:56 PM, Geert Uytterhoeven
> wrote:
>> On Thu, Sep 15, 2011 at 19:52, Alex Deucher
wrote:
>>> While the DRM has historical
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
>> understa
On 09/15/2011 05:52 PM, Alex Deucher wrote:
> On Thu, Sep 15, 2011 at 1:12 PM, Florian Tobias Schandinat
> wrote:
>> On 09/15/2011 03:50 PM, Keith Packard wrote:
>>> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
>>> wrote:
>>>
1) It's part of DRM, so it doesn't help fb or v4l2 drivers.
On Thu, Sep 15, 2011 at 1:56 PM, Geert Uytterhoeven
wrote:
> On Thu, Sep 15, 2011 at 19:52, Alex Deucher 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
On Thu, Sep 15, 2011 at 1:12 PM, Florian Tobias Schandinat
wrote:
> On 09/15/2011 03:50 PM, Keith Packard wrote:
>> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
>> 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
On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
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 like to think we could
On Thu, Sep 15, 2011 at 19:52, Alex Deucher 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 to modern hardware
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
>> infrastru
On 09/15/2011 03:50 PM, Keith Packard wrote:
> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
> 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 v4
> 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 15 September 2011 15:58, James Westby wrote:
> On Thu, 15 Sep 2011 15:08:26 -0500, Zach Pfeffer
> 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 extrac
On Thu, 15 Sep 2011 15:08:26 -0500, Zach Pfeffer
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. I thought, it may m
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
> 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 me
> 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
> 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 additions were needed for some specia
On Thu, Sep 15, 2011 at 12:21 PM, Tomi Valkeinen wrote:
> On Thu, 2011-09-15 at 10:50 -0500, Keith Packard wrote:
>> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
>> 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 Li
> 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 dis
>Sorry, who is working on this and when is it going back in? perf is a
>significant feature and Panda is a very common board...
>
>-- Michael
I have been unable to reproduce the boot hang problem after unreverting
the interrupt patch. Can those experiencing it please verify they are
using the l
On Thu, 2011-09-15 at 10:50 -0500, Keith Packard wrote:
> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
> 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,
> 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 c
On Thu, 15 Sep 2011 10:50:32 -0500
Keith Packard wrote:
> On Thu, 15 Sep 2011 18:29:54 +0300, Tomi Valkeinen
> 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 buil
On Thu, 2011-09-15 at 09:59 -0500, Keith Packard wrote:
> On Thu, 15 Sep 2011 15:07:05 +0300, Tomi Valkeinen
> 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
On Thu, 15 Sep 2011 15:07:05 +0300, Tomi Valkeinen
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 environment. This is pretty
Hi Tomi,
On Thu, Sep 15, 2011 at 9:07 PM, Tomi Valkeinen 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 already, but I
> neve
Hello Michael,
On Tue, 06 Sep 2011 08:35:57 +1200
Michael Hudson-Doyle wrote:
> On Mon, 5 Sep 2011 16:18:34 +0300, Paul Sokolovsky
> wrote:
> > Hello,
> >
> > We're running Jenkins EC2 plugin v 1.11 on android-build.linaro.org,
> > which is 2 releases behind the latest 1.13. Per ChangeLog, it
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 presen
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 sh
Dear Wolfgang Denk,
On Thursday 15 September 2011 02:44 PM, Wolfgang Denk wrote:
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.
...
+s
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 woul
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 = {
> +
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
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
---
Changes for V4:
* Added gpio_free() call
* Removed .refresh value as it was same as default valu
39 matches
Mail list logo
