On Mon, Nov 26, 2012 at 2:45 PM, Otavio Salvador
<otavio@...> wrote:

Two additional questions:
- Has anyone tested "egl on fb" (without x11) with this new drivers?
(so far I've only tested it with 12.04.01)

Daiane has tested it I think. Daiane?

I tested tiger (under /opt/viv_samples) (and cover flow) and it worked
very fine. I tested it on X11 image and with fb image.

Do you think this test is enough? What would be other good tests?

Daiane

On Mon, Nov 26, 2012 at 3:00 PM, Daiane Angolini <daiane.list@...> wrote:

On Mon, Nov 26, 2012 at 2:45 PM, Otavio Salvador
<otavio@...> wrote:

Two additional questions:
- Has anyone tested "egl on fb" (without x11) with this new drivers?
(so far I've only tested it with 12.04.01)

Daiane has tested it I think. Daiane?

I tested tiger (under /opt/viv_samples) (and cover flow) and it worked
very fine. I tested it on X11 image and with fb image.

Do you think this test is enough? What would be other good tests?

Later Qt will prove if it works or not ;-)

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, Nov 26, 2012 at 2:53 PM, Thomas Senyk
<thomas.senyk@...> wrote:

On Mon, November 26, 2012 14:00:42 Daiane Angolini wrote:

On Mon, Nov 26, 2012 at 2:45 PM, Otavio Salvador

<otavio@...> wrote:

Two additional questions:
- Has anyone tested "egl on fb" (without x11) with this new drivers?

(so far I've only tested it with 12.04.01)

Daiane has tested it I think. Daiane?

I tested tiger (under /opt/viv_samples) (and cover flow) and it worked
very fine. I tested it on X11 image and with fb image.

Do you think this test is enough? What would be other good tests?

Yes @ "enough" .. at least for me to do the next bigger test: Qt5 and eglfs
plugin.
I'll do this test as soon as I get my board back! :)

By the way, HP people, Martin and I are working in Qt5 packaging for
OE. We're doing our work at https://github.com/meta-qt5/meta-qt5

It is not yet working but you might want to help ;-)

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, November 26, 2012 15:12:08 Otavio Salvador wrote:

On Mon, Nov 26, 2012 at 2:53 PM, Thomas Senyk

<thomas.senyk@...> wrote:

On Mon, November 26, 2012 14:00:42 Daiane Angolini wrote:

On Mon, Nov 26, 2012 at 2:45 PM, Otavio Salvador

<otavio@...> wrote:

Two additional questions:
- Has anyone tested "egl on fb" (without x11) with this new drivers?

(so far I've only tested it with 12.04.01)

Daiane has tested it I think. Daiane?

I tested tiger (under /opt/viv_samples) (and cover flow) and it worked
very fine. I tested it on X11 image and with fb image.

Do you think this test is enough? What would be other good tests?

Yes @ "enough" .. at least for me to do the next bigger test: Qt5 and
eglfs
plugin.
I'll do this test as soon as I get my board back! :)

By the way, HP people, Martin and I are working in Qt5 packaging for
OE. We're doing our work at https://github.com/meta-qt5/meta-qt5

Nice!! I took a quick look at the files ...and as with the qt4 recipes, it's
... interesting ... how complex things can get when writing a recipe ;)

I'll test it tomorrow ... I guess the proper channel to talk about this is
openembedded-devel@... ?

Greets
Thomas

It is not yet working but you might want to help ;-)

Signed-off-by: Alexandre Belloni <alexandre.belloni@...>
---
.../gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc | 3 +++
1 file changed, 3 insertions(+)

diff --git a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
index 83ab75a..4baf608 100644
--- a/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
+++ b/recipes-graphics/gpu-viv-bin-mx6q/gpu-viv-bin-mx6q.inc
@@ -33,6 +33,9 @@ PACKAGES =+ "libclc-mx6 libclc-mx6-dev libclc-mx6-dbg \
libvivante-common-mx6 libvivante-common-mx6-dev libvivante-common-mx6-dbg \
"

+# Inhibit warnings about files being stripped.
+INHIBIT_PACKAGE_DEBUG_SPLIT = "1"
+
# FIXME: The provided binary doesn't provide soname. If in future BSP
# release the libraries are fixed, we can drop this hack.
SOLIBS = "${SOLIBSDEV}"
--
1.7.9.5

On 2012-11-26 09:45, Otavio Salvador wrote:

On Mon, Nov 26, 2012 at 2:23 PM, Thomas Senyk
<thomas.senyk@...> wrote:

I've just tested a 'bitbake core-image-x11' and it builds without any problem.

I got a couple of warnings such as:
WARNING: File '/opt/viv_samples/vdk/tutorial2' from gpu-viv-bin-mx6q was
already stripped, this will prevent future debugging!

... I don't mind them, but "silencing" them would be helpful/good enough
(no clue if this is possible/feasible)

I did a brief check how to quiet them but didn't find a way so I let
them on for now.

I would like to tell you that I've also tested this on the hardware, but it my
imx6 got "stolen" by colleagues ;)

Please do! :)

I've tried these new changes on my imx6qsabrelite board and X now comes up (no
more segmentation violation), but the touch screen isn't working. I don't see
a module available for it (it used to be tsc2004).

How do I get the touch screen going?

Thanks

I'm using LVDS and it is not working as well.

I don't know tsc2004, where do you connect this display?

You could try to use egalaxy driver, may you do that? (and let me know
the results =P)


Daiane

On Mon, Nov 26, 2012 at 3:48 PM, Thomas Senyk
<thomas.senyk@...> wrote:

On Mon, November 26, 2012 15:12:08 Otavio Salvador wrote:

On Mon, Nov 26, 2012 at 2:53 PM, Thomas Senyk

<thomas.senyk@...> wrote:

On Mon, November 26, 2012 14:00:42 Daiane Angolini wrote:

On Mon, Nov 26, 2012 at 2:45 PM, Otavio Salvador

<otavio@...> wrote:

Two additional questions:
- Has anyone tested "egl on fb" (without x11) with this new drivers?

(so far I've only tested it with 12.04.01)

Daiane has tested it I think. Daiane?

I tested tiger (under /opt/viv_samples) (and cover flow) and it worked
very fine. I tested it on X11 image and with fb image.

Do you think this test is enough? What would be other good tests?

Yes @ "enough" .. at least for me to do the next bigger test: Qt5 and
eglfs
plugin.
I'll do this test as soon as I get my board back! :)

By the way, HP people, Martin and I are working in Qt5 packaging for
OE. We're doing our work at https://github.com/meta-qt5/meta-qt5

Nice!! I took a quick look at the files ...and as with the qt4 recipes, it's
... interesting ... how complex things can get when writing a recipe ;)

I'll test it tomorrow ... I guess the proper channel to talk about this is
openembedded-devel@... ?

In fact we've been discussing it at oe@...

The recipes are not working for non x86 targets as it is still trying
to run native tools during target builds. It is still work in progress
but any help is good.

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, Nov 26, 2012 at 3:56 PM, Alexandre Belloni
<alexandre.belloni@...> wrote:

Signed-off-by: Alexandre Belloni <alexandre.belloni@...>

Good catch! Did you check the code if it will warn if it has debug
symbols in the package? My concern here is if examples or other apps
has symbols if it is going to warn so we can fix it.

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On 2012-11-26 11:04, Daiane Angolini wrote:

I'm using LVDS and it is not working as well.

I don't know tsc2004, where do you connect this display?

You could try to use egalaxy driver, may you do that? (and let me know
the results =P)

That driver is compiled in and it's trying to use it, but failing.
I get this error when I boot:
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5

I had this working with a previous kernel, using these modules:
egalax_ts
tsc2004
galcore

n.b. when you reply, please quote what you are replying to. If you
read these messages via email (as I do), all context is lost and it's
really hard to figure out what you are saying. Not everyone uses
Google Group's swank interface!

On Mon, Nov 26, 2012 at 04:21:24PM -0200, Otavio Salvador wrote :

Good catch! Did you check the code if it will warn if it has debug
symbols in the package? My concern here is if examples or other apps
has symbols if it is going to warn so we can fix it.

I don't think so but I haven't checked. I'm wondering if we shouldn't
separate the driver itself from the example applications that are in
/opt. I don't think you would want those on your final production
releases...

--
Alexandre Belloni

On Mon, Nov 26, 2012 at 4:21 PM, Otavio Salvador
<otavio@...> wrote:

On Mon, Nov 26, 2012 at 3:56 PM, Alexandre Belloni
<alexandre.belloni@...> wrote:

Signed-off-by: Alexandre Belloni <alexandre.belloni@...>

Good catch! Did you check the code if it will warn if it has debug
symbols in the package? My concern here is if examples or other apps
has symbols if it is going to warn so we can fix it.

Looking at the python code it seems we ought to use:

INHIBIT_PACKAGE_STRIP = "1"

Regarding your patch, please:

* bump INC_PR;
* prefix short commit description with the recipe name you are changing;

Thanks by looking at it.

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, Nov 26, 2012 at 4:33 PM, Alexandre Belloni
<alexandre.belloni@...> wrote:

On Mon, Nov 26, 2012 at 04:21:24PM -0200, Otavio Salvador wrote :

Good catch! Did you check the code if it will warn if it has debug
symbols in the package? My concern here is if examples or other apps
has symbols if it is going to warn so we can fix it.

I don't think so but I haven't checked. I'm wondering if we shouldn't
separate the driver itself from the example applications that are in
/opt. I don't think you would want those on your final production
releases...

It has been done that way; the driver files are split among many
lib<something> files and the example code in ${PN}. So it should be
fine.

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, Nov 26, 2012 at 4:27 PM, Gary Thomas <samoht.yrag@...> wrote:

On 2012-11-26 11:04, Daiane Angolini wrote:

I'm using LVDS and it is not working as well.

I don't know tsc2004, where do you connect this display?

You could try to use egalaxy driver, may you do that? (and let me know
the results =P)

That driver is compiled in and it's trying to use it, but failing.
I get this error when I boot:
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5

I had this working with a previous kernel, using these modules:
egalax_ts
tsc2004

Right.

galcore

This is now built-in.

Since you had it working previously please compare the dmesg output
between both kernels so we can have a light where to look for it?

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On 2012-11-26 11:40, Otavio Salvador wrote:

On Mon, Nov 26, 2012 at 4:27 PM, Gary Thomas <samoht.yrag@...> wrote:

On 2012-11-26 11:04, Daiane Angolini wrote:

I'm using LVDS and it is not working as well.

I don't know tsc2004, where do you connect this display?

You could try to use egalaxy driver, may you do that? (and let me know
the results =P)

That driver is compiled in and it's trying to use it, but failing.
I get this error when I boot:
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5

I had this working with a previous kernel, using these modules:
egalax_ts
tsc2004

Right.

galcore

This is now built-in.

Since you had it working previously please compare the dmesg output
between both kernels so we can have a light where to look for it?

I'll see what I can do. I built it using meta-fsl-arm in October, so
I'll have to rewind meta-fsl-arm to that time period since the linux
kernel recipes have been updated (and older versions deleted).

Does someone have a working image for the sabrelite that uses this
touch screen (it was the only one available as I recall when I bought
the board in October)? I'd really like to try a known image so as to
eliminate any errors I might have added when making the build.

On Mon, Nov 26, 2012 at 4:54 PM, Gary Thomas <samoht.yrag@...> wrote:

On 2012-11-26 11:40, Otavio Salvador wrote:

On Mon, Nov 26, 2012 at 4:27 PM, Gary Thomas <samoht.yrag@...>
wrote:

On 2012-11-26 11:04, Daiane Angolini wrote:

I'm using LVDS and it is not working as well.

I don't know tsc2004, where do you connect this display?

You could try to use egalaxy driver, may you do that? (and let me know
the results =P)

That driver is compiled in and it's trying to use it, but failing.
I get this error when I boot:
egalax_ts 2-0004: egalax_ts: failed to read firmware version
egalax_ts: probe of 2-0004 failed with error -5

I had this working with a previous kernel, using these modules:
egalax_ts
tsc2004

Right.

galcore

This is now built-in.

Since you had it working previously please compare the dmesg output
between both kernels so we can have a light where to look for it?

I'll see what I can do. I built it using meta-fsl-arm in October, so
I'll have to rewind meta-fsl-arm to that time period since the linux
kernel recipes have been updated (and older versions deleted).

Does someone have a working image for the sabrelite that uses this
touch screen (it was the only one available as I recall when I bought
the board in October)? I'd really like to try a known image so as to
eliminate any errors I might have added when making the build.

In any case this seems to be kernel related and not a BSP issue.
Fabio, could you take a look?

--
Otavio Salvador O.S. Systems
E-mail: otavio@... http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br

On Mon, Nov 26, 2012 at 04:35:24PM -0200, Otavio Salvador wrote :

It has been done that way; the driver files are split among many
lib<something> files and the example code in ${PN}. So it should be
fine.

Yeah right, I didn't read the inc file to the end...

--
Alexandre Belloni

On Mon, Nov 26, 2012 at 5:30 AM, Daiane Angolini <daiane.list@...> wrote:

As a final tip, use a layer for your/your customer changes so your
maintenance work will be much easier.

Gopi, you can take a look how meta-fsl-demos is used combined with
meta-fsl-arm, and create one meta-gopi in order to include your own
packages.

Or meta-fsl-ppc instead of meta-fsl-arm for p2041rdb ;)

-M

On Fri, Nov 23, 2012 at 5:37 AM, Otavio Salvador
<otavio@...> wrote:

On Fri, Nov 23, 2012 at 8:10 AM, Zhenhua Luo <b19537@...> wrote:

upgrade the version to 2.9.0 to fix following version mismatch issue:
ERROR: No recipes available for:
/srv/home/pokybuild/yocto-autobuilder/yocto-slave/p1022ds/build/yocto/meta-fsl-ppc/recipes-append/libxml/libxml2_2.8.0.bbappend

[YOCTO #3476]

Signed-off-by: Zhenhua Luo <b19537@...>

Before this patch is applied, the danny branch of meta-fsl-ppc needs
to be created or we will break danny support.

danny is already there in meta-fsl-ppc

I've queued this up for testing.

-M

On Mon, Nov 26, 2012 at 04:34:24PM -0200, Otavio Salvador wrote :

On Mon, Nov 26, 2012 at 4:21 PM, Otavio Salvador
<otavio@...> wrote:

On Mon, Nov 26, 2012 at 3:56 PM, Alexandre Belloni
<alexandre.belloni@...> wrote:

Signed-off-by: Alexandre Belloni <alexandre.belloni@...>

Good catch! Did you check the code if it will warn if it has debug
symbols in the package? My concern here is if examples or other apps
has symbols if it is going to warn so we can fix it.

Looking at the python code it seems we ought to use:

INHIBIT_PACKAGE_STRIP = "1"

Just to be clear, you mean you want to use both
INHIBIT_PACKAGE_DEBUG_SPLIT = 1, to solve the warning issue and
INHIBIT_PACKAGE_STRIP = 1 ?

If I'm not mistaken, this will mean that unstripped binaries won't get
stripped. Is that what you want ?

Regarding your patch, please:

* bump INC_PR;
* prefix short commit description with the recipe name you are changing;

Will do.

Regards,

--
Alexandre Belloni