sstate black hole?
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi
x86_64-linux
The packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Hi Gary,
Quoted 23 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.
Quoted 2 lines
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Are these packages (the ones that are getting rebuilt) depending on machine-specific headers (kernel)?
Regards,
Nikolay
Quoted 23 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.
Quoted 2 lines
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Use openembedded-core/scripts/sstate-diff-machines.sh to check if the signatures of the recipes you expect to be re-used are the same.
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 24 lines · Martin Jansa
Quoted 23 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.
Quoted 6 lines
Quoted 2 lines
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Use
openembedded-core/scripts/sstate-diff-machines.shto check if the signatures of the recipes you expect to be re-used are the same.
How can I use this if the two targets have their own tmp/ tree?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 25 lines · Gary Thomas
Quoted 24 lines · Martin Jansa
Quoted 23 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Use
openembedded-core/scripts/sstate-diff-machines.shto check if the signatures of the recipes you expect to be re-used are the same.How can I use this if the two targets have their own tmp/ tree?
call it twice (once in each tmp tree) and compare resulting list.M files
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]
Quoted 29 lines · Martin Jansa
Quoted 28 lines · Gary Thomas
Quoted 27 lines · Martin Jansa
Quoted 25 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Use
openembedded-core/scripts/sstate-diff-machines.shto check if the signatures of the recipes you expect to be re-used are the same.How can I use this if the two targets have their own tmp/ tree?
call it twice (once in each tmp tree) and compare resulting list.M files
Sadly, that script seems to destroy all of the .sigdata files which are needed to actually track down the culprit(s).
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 34 lines · Gary Thomas
Quoted 33 lines · Martin Jansa
Quoted 32 lines · Gary Thomas
Quoted 30 lines · Martin Jansa
Quoted 23 lines · Gary Thomas
I'm working with i.MX6 targets (meta-fsl-arm*). For these targets, some packages are "special" in that they use i.MX6 specific graphics support. This ends up with an additional layer of stratification, so my tmp/work tree has:
all-amltd-linux cortexa9hf-vfp-neon-amltd-linux-gnueabi cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi teton_p0382-amltd-linux-gnueabi x86_64-amltd-linux-gnueabi x86_64-linuxThe packages that are built in tmp/work/cortex* are architecture specific, not target specific, hence my question:
If I build for two i.MX6 targets, identical in every way except for the ${MACHINE} name, if I use sstate to share
the builds from target A when building for target B, why
are the packages built in cortexa9hf-vfp-neon-mx6qdl-amltd-linux-gnueabi not shared by sstate? I can see that they are present in the sstate cache, but they are always rebuilt for target B. I consider this incorrect behaviour as these are the same architecture and so they should be sharable via sstate.Quoted 2 lines
Am I missing something here? How can I determine why the package from target A (sstate cache) is not usable by target B?
Use
openembedded-core/scripts/sstate-diff-machines.shto check if the signatures of the recipes you expect to be re-used are the same.
Quoted 8 lines
Quoted 4 lines
Quoted 1 line
How can I use this if the two targets have their own tmp/ tree?
call it twice (once in each tmp tree) and compare resulting list.M files
Sadly, that script seems to destroy all of the .sigdata files which are needed to actually track down the culprit(s).
I followed this down to an i.MX6 specific package which is
in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/egl virtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2'
to
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/egl virtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1
virtual/libgles2'
Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/egl virtual/libopenvg virtual/libg2d" PROVIDES_append_mx6q = " virtual/libgl virtual/libgles1 virtual/libgles2" PROVIDES_append_mx6dl = " virtual/libgl virtual/libgles1 virtual/libgles2" PROVIDES_append_mx6sx = " virtual/libgl virtual/libgles1 virtual/libgles2"
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q and mx6dl, hence the duplication.
Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 23 lines · On Monday 15 June 2015 18:19:21 Gary Thomas wrote:
I followed this down to an i.MX6 specific package which is in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/egl
virtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2' to
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/egl
virtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1 virtual/libgles2'Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d"
PROVIDES_append_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2"
Quoted 6 lines
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q and mx6dl, hence the duplication.
Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
I agree this would be nice, but for this to work we'd probably need to introduce a typing system within bitbake so that it can understand that this variable is a space-separated list. That is something we will probably do at some point for a variety of reasons, but I don't know that it's something we will get to soon.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 31 lines · Paul Eggleton
Quoted 23 lines · On Monday 15 June 2015 18:19:21 Gary Thomas wrote:
I followed this down to an i.MX6 specific package which is in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/egl
virtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2' to'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1 virtual/libgles2'
Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d"
PROVIDES_append_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2"Quoted 6 lines
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q and mx6dl, hence the duplication.
Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
Quoted 5 lines
I agree this would be nice, but for this to work we'd probably need to introduce a typing system within bitbake so that it can understand that this variable is a space-separated list. That is something we will probably do at some point for a variety of reasons, but I don't know that it's something we will get to soon.
Is there some way to solve this in the recipe itself? I can see that it needs to make sure that those values are provided for each of the [sub]class of processor, but is there a way to write it so that they are only added once? Perhaps a little bit of Python magic?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 47 lines · On Tuesday 16 June 2015 04:47:53 Gary Thomas wrote:
Quoted 40 lines · Paul Eggleton
Quoted 32 lines · On Monday 15 June 2015 18:19:21 Gary Thomas wrote:
I followed this down to an i.MX6 specific package which is
in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2' to
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1 virtual/libgles2'
Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains
these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d"
PROVIDES_append_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2"Quoted 6 lines
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q and mx6dl, hence the duplication.
Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
Quoted 5 lines
I agree this would be nice, but for this to work we'd probably need to introduce a typing system within bitbake so that it can understand that this variable is a space-separated list. That is something we will probably do at some point for a variety of reasons, but I don't know that it's something we will get to soon.
Quoted 4 lines
Is there some way to solve this in the recipe itself? I can see that it needs to make sure that those values are provided for each of the [sub]class of processor, but is there a way to write it so that they are only added once? Perhaps a little bit of Python magic?
Sure, you could use an anonymous python function with actual conditional statements instead of overrides to set PROVIDES here.
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre
Quoted 48 lines · Paul Eggleton
Quoted 47 lines · On Tuesday 16 June 2015 04:47:53 Gary Thomas wrote:
Quoted 45 lines · Paul Eggleton
Quoted 32 lines · On Monday 15 June 2015 18:19:21 Gary Thomas wrote:
I followed this down to an i.MX6 specific package which is
in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2' to
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1 virtual/libgles2'
Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains
these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d"
PROVIDES_append_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2"Quoted 6 lines
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q and mx6dl, hence the duplication.
Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
I agree this would be nice, but for this to work we'd probably need to introduce a typing system within bitbake so that it can understand that this variable is a space-separated list. That is something we will probably do at some point for a variety of reasons, but I don't know that it's something we will get to soon.
Quoted 7 lines
Quoted 4 lines
Is there some way to solve this in the recipe itself? I can see that it needs to make sure that those values are provided for each of the [sub]class of processor, but is there a way to write it so that they are only added once? Perhaps a little bit of Python magic?
Sure, you could use an anonymous python function with actual conditional statements instead of overrides to set PROVIDES here.
Thanks. I found a much simpler way - I replaced the previous version by:
EXTRA_PROVIDES = ""
EXTRA_PROVIDES_mx6q = " virtual/libgl virtual/libgles1 virtual/libgles2"
EXTRA_PROVIDES_mx6dl = " virtual/libgl virtual/libgles1 virtual/libgles2"
EXTRA_PROVIDES_mx6sx = " virtual/libgl virtual/libgles1 virtual/libgles2"
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/egl virtual/libopenvg virtual/libg2d ${EXTRA_PROVIDES}"
If the additions were unique, i.e. _mx6q was somehow different from _mx6dl, I would have had to use the python function, but since they are all the same this simpler way works just fine.
Thanks for the pointers
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 68 lines · On Tuesday 16 June 2015 07:21:05 Gary Thomas wrote:
Quoted 51 lines · Paul Eggleton
Quoted 50 lines · On Tuesday 16 June 2015 04:47:53 Gary Thomas wrote:
Quoted 48 lines · Paul Eggleton
Quoted 33 lines · On Monday 15 June 2015 18:19:21 Gary Thomas wrote:
I followed this down to an i.MX6 specific package which is
in DEPENDS:
Variable PROVIDES value changed from
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2' to
'${PN} virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d virtual/libgl virtual/libgles1 virtual/libgles2 virtual/libgl virtual/libgles1 virtual/libgles2'
Why aren't these considered the same (duplicate elements and/or order) should not matter for PROVIDES. Is there some way we could get bitbake to collapse this and remove the duplicates?
I found that this happens in meta-fsl-arm:recipes-graphics/imx-gpu-viv/imx-gpu-viv.inc which contains
these lines:
PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/eglvirtual/libopenvg virtual/libg2d"
PROVIDES_append_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"PROVIDES_append_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2"Quoted 7 lines
Some i.MX6 targets, nitrogen6x in particular, has overrides for both mx6q
and mx6dl, hence the duplication.Note: I removed the extra override (for testing) and found that now the packages built by target A can be shared via sstate with target B (at least the few I tested)
I agree this would be nice, but for this to work we'd probably need to introduce a typing system within bitbake so that it can understand that this variable is a space-separated list. That is something we will probably do at some point for a variety of reasons, but I don't know that
it's something we will get to soon.Quoted 7 lines
Quoted 4 lines
Is there some way to solve this in the recipe itself? I can see that it needs to make sure that those values are provided for each of the [sub]class of processor, but is there a way to write it so that they are only added once? Perhaps a little bit of Python magic?
Sure, you could use an anonymous python function with actual conditional statements instead of overrides to set PROVIDES here.
Thanks. I found a much simpler way - I replaced the previous version by:
EXTRA_PROVIDES= ""
EXTRA_PROVIDES_mx6q= " virtual/libgl virtual/libgles1 virtual/libgles2"EXTRA_PROVIDES_mx6dl= " virtual/libgl virtual/libgles1 virtual/libgles2"EXTRA_PROVIDES_mx6sx= " virtual/libgl virtual/libgles1 virtual/libgles2" PROVIDES += "virtual/wayland-egl virtual/libgal-x11 virtual/egl virtual/libopenvg virtual/libg2d ${EXTRA_PROVIDES}"
Quoted 3 lines
If the additions were unique, i.e.
_mx6qwas somehow different from_mx6dl, I would have had to use the python function, but since they are all the same this simpler way works just fine.
Yep, that will work too - good job :)
Cheers,
Paul
Signature · 2 lines
Paul Eggleton Intel Open Source Technology Centre