[PATCH] beagleboard-test-image: add g_ether kernel module

[PATCH] beagleboard-test-image: add g_ether kernel module

[Jason Kridner]

Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
---
 recipes/images/beagleboard-test-image.bb |    1 +
 1 files changed, 1 insertions(+), 0 deletions(-)

diff --git a/recipes/images/beagleboard-test-image.bb b/recipes/images/beagleboard-test-image.bb
index cbb2e7d..71cbbab 100644
--- a/recipes/images/beagleboard-test-image.bb
+++ b/recipes/images/beagleboard-test-image.bb
@@ -20,6 +20,7 @@ IMAGE_INSTALL += " \
   nano \
   cpuburn-neon \
   kernel-module-mt9t112 \
+  kernel-module-g-ether \
   u-boot-mkimage \
   sox \
   devmem2 \
-- 
1.5.6.4

[PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Jason Kridner]

I want to use the name beagleboard-demo-image for what actually ships
with the xM boards.

Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
---
 recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
 1 files changed, 30 insertions(+), 0 deletions(-)
 create mode 100644 recipes/images/beagleboard-olddemo-image.bb

diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
new file mode 100644
index 0000000..d83281c
--- /dev/null
+++ b/recipes/images/beagleboard-olddemo-image.bb
@@ -0,0 +1,30 @@
+# Demo image for beagleboard
+
+IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
+
+XSERVER ?= "xserver-xorg \
+           xf86-input-evdev \
+           xf86-input-mouse \
+           xf86-video-fbdev \
+           xf86-input-keyboard \
+"
+
+ANGSTROM_EXTRA_INSTALL ?= ""
+SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
+
+export IMAGE_BASENAME = "Beagleboard-demo-image"
+
+DEPENDS = "task-base"
+IMAGE_INSTALL = "\
+    ${XSERVER} \
+    ${ANGSTROM_EXTRA_INSTALL} \
+    task-beagleboard-demo \
+    ${SPLASH} \
+    "
+
+IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
+
+#zap root password for release images
+ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
+
+inherit image
-- 
1.5.6.4

[PATCH] beagleboard-demo-image: add packages used at ESC

[Jason Kridner]

* nodejs and linuxtag-ics don't seem to have cross-compiling recipes to create them.
* esc-node-demo requries nodejs

Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
---
 recipes/images/beagleboard-demo-image.bb |  101 ++++++++++++++++++++++++++++++
 1 files changed, 101 insertions(+), 0 deletions(-)

diff --git a/recipes/images/beagleboard-demo-image.bb b/recipes/images/beagleboard-demo-image.bb
index d83281c..5d36dea 100644
--- a/recipes/images/beagleboard-demo-image.bb
+++ b/recipes/images/beagleboard-demo-image.bb
@@ -6,6 +6,7 @@ XSERVER ?= "xserver-xorg \
            xf86-input-evdev \
            xf86-input-mouse \
            xf86-video-fbdev \
+           xf86-video-sisusb \
            xf86-input-keyboard \
 "
 
@@ -20,10 +21,110 @@ IMAGE_INSTALL = "\
     ${ANGSTROM_EXTRA_INSTALL} \
     task-beagleboard-demo \
     ${SPLASH} \
+    bash \
+    gstreamer-ti \
+    libgles-omap3-x11wsegl \
+    shadow \
+    bash \
+    psplash-angstrom \
+    task-base-extended \
+    angstrom-task-gnome \
+    ti-dsplink-examples \
+    ti-codec-engine-examples \
+    ti-dmai-apps \
+    gstreamer-ti \
+    libgles-omap3-x11wsegl \
+    bc-cube-fb \
+    bc-cube-x11 \
+    mplayer \
+    omapfbplay \
+    cpufrequtils \
+    htop \
+    powertop \
+    ntpdate \
+    libgles-omap3-rawdemos \
+    libgles-omap3-x11demos \
+    abiword \
+    gnumeric \
+    epiphany \
+    memtester \
+    kernel-modules \
+    epiphany \
+    midori \
+    firefox \
+    gnome-mplayer \
+    gecko-mediaplayer-firefox-hack \
+    gpe-scap \
+    gst-plugin-gles \
+    alsa-utils \
+    alsa-utils-alsamixer \
+    alsa-utils-aplay \
+    alsa-utils-amixer \
+    alsa-utils-aconnect \
+    alsa-utils-iecset \
+    alsa-utils-speakertest \
+    alsa-utils-aseqnet \
+    alsa-utils-aseqdump \
+    alsa-utils-alsaconf \
+    alsa-utils-alsactl \
+    ti-msp430-chronos-apps \
+    git \
+    vim \
+    screen \
+    dosfstools \
+    omap-dss-doc \
+    gedit \
+    lsof \
+    matrix-gui \
+    matrix-tui \
+    am-benchmarks \
+    am-sysinfo \
+    e2fsprogs \
+    e2fsprogs-mke2fs \
+    nano \
+    qt4-demos \
+    qt4-plugin-imageformat-jpeg \
+    qt4-plugin-imageformat-svg \
+    qt-x11-qvfb \
+    qt4-embedded-demos \
+    qt4-embedded-plugin-gfxdriver-gfxvnc \
+    qt4-embedded-plugin-gfxdriver-gfxtransformed \
+    qt4-embedded \
+    qt4-embedded-fonts \
+    qt4-embedded-plugin-imageformat-svg \
+    qt4-embedded-plugin-imageformat-jpeg \
+    arora \
+    arora-e \
+    task-native-sdk \
+    task-qte-toolchain-target \
+    qt4-x11-free-gles-dev \
+    u-boot-mkimage \
+    picodlp-control \
+    x-load \
+    u-boot \
+    angstrom-uboot-scripts \
+    x11vnc \
+    evtest \
+    gstd \
+    qmake2 \
+    matrix-gui-autostart \
+    esc-gst \
+    esc-media \
+#    nodejs \
+#    esc-node-demo \
+    mtd-utils \
+    i2c-tools \
+    beagleboard-test-scripts \
+    cpuburn-neon \
+    sox \
+    devmem2 \
     "
 
 IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
 
+IMAGE_LOGIN_MANAGER = "shadow"
+IMAGE_SPLASH = "psplash-angstrom"
+
 #zap root password for release images
 ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
 
-- 
1.5.6.4

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Frans Meulenbroeks]

2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
> I want to use the name beagleboard-demo-image for what actually ships
> with the xM boards.
>
> Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
> ---
>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
>  1 files changed, 30 insertions(+), 0 deletions(-)
>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
>
> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
> new file mode 100644
> index 0000000..d83281c
> --- /dev/null
> +++ b/recipes/images/beagleboard-olddemo-image.bb
> @@ -0,0 +1,30 @@
> +# Demo image for beagleboard
> +
> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
> +
> +XSERVER ?= "xserver-xorg \
> +           xf86-input-evdev \
> +           xf86-input-mouse \
> +           xf86-video-fbdev \
> +           xf86-input-keyboard \
> +"
> +
> +ANGSTROM_EXTRA_INSTALL ?= ""
> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
> +
> +export IMAGE_BASENAME = "Beagleboard-demo-image"
> +
> +DEPENDS = "task-base"
> +IMAGE_INSTALL = "\
> +    ${XSERVER} \
> +    ${ANGSTROM_EXTRA_INSTALL} \
> +    task-beagleboard-demo \
> +    ${SPLASH} \
> +    "
> +
> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
> +
> +#zap root password for release images
> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
> +
> +inherit image
> --

What about a better name? E.g. XM-demo-iimage?

And to widen the question: do we want to maintain customer/supplier
specific images in the oe repo?
The company I work for also has some images, but for now we opted to
keep them in a private overlay.

Frans

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Jason Kridner]

On Tue, Aug 17, 2010 at 3:54 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
>> I want to use the name beagleboard-demo-image for what actually ships
>> with the xM boards.
>>
>> Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
>> ---
>>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
>>  1 files changed, 30 insertions(+), 0 deletions(-)
>>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
>>
>> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
>> new file mode 100644
>> index 0000000..d83281c
>> --- /dev/null
>> +++ b/recipes/images/beagleboard-olddemo-image.bb
>> @@ -0,0 +1,30 @@
>> +# Demo image for beagleboard
>> +
>> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
>> +
>> +XSERVER ?= "xserver-xorg \
>> +           xf86-input-evdev \
>> +           xf86-input-mouse \
>> +           xf86-video-fbdev \
>> +           xf86-input-keyboard \
>> +"
>> +
>> +ANGSTROM_EXTRA_INSTALL ?= ""
>> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
>> +
>> +export IMAGE_BASENAME = "Beagleboard-demo-image"
>> +
>> +DEPENDS = "task-base"
>> +IMAGE_INSTALL = "\
>> +    ${XSERVER} \
>> +    ${ANGSTROM_EXTRA_INSTALL} \
>> +    task-beagleboard-demo \
>> +    ${SPLASH} \
>> +    "
>> +
>> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
>> +
>> +#zap root password for release images
>> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
>> +
>> +inherit image
>> --
>
> What about a better name? E.g. XM-demo-iimage?

I don't know why we need two demo images.  This should run on Rev Cx as well.

>
> And to widen the question: do we want to maintain customer/supplier
> specific images in the oe repo?
> The company I work for also has some images, but for now we opted to
> keep them in a private overlay.

I want this to be public and part of the mainline to make it easy for
people to reproduce.  It is for a relatively broad target.  Is there a
reason it shouldn't be there?

>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Philip Balister]

On 08/17/2010 12:54 PM, Frans Meulenbroeks wrote:
> 2010/8/17 Jason Kridner<jkridner@beagleboard.org>:
>> I want to use the name beagleboard-demo-image for what actually ships
>> with the xM boards.

....

>> +inherit image
>> --
>
> What about a better name? E.g. XM-demo-iimage?
>
> And to widen the question: do we want to maintain customer/supplier
> specific images in the oe repo?
> The company I work for also has some images, but for now we opted to
> keep them in a private overlay.

In this case, beagleboard.org points people at oe dev to do builds, so 
it is appropriate to have this image in dev.

I do think they should just edit the existing file, no need to save the 
old one. I suspect that 90% of people using the beagle build images from 
narcissus anyway.

Philip

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Frans Meulenbroeks]

2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
> On Tue, Aug 17, 2010 at 3:54 PM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
>> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
>>> I want to use the name beagleboard-demo-image for what actually ships
>>> with the xM boards.
>>>
>>> Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
>>> ---
>>>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
>>>  1 files changed, 30 insertions(+), 0 deletions(-)
>>>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
>>>
>>> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
>>> new file mode 100644
>>> index 0000000..d83281c
>>> --- /dev/null
>>> +++ b/recipes/images/beagleboard-olddemo-image.bb
>>> @@ -0,0 +1,30 @@
>>> +# Demo image for beagleboard
>>> +
>>> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
>>> +
>>> +XSERVER ?= "xserver-xorg \
>>> +           xf86-input-evdev \
>>> +           xf86-input-mouse \
>>> +           xf86-video-fbdev \
>>> +           xf86-input-keyboard \
>>> +"
>>> +
>>> +ANGSTROM_EXTRA_INSTALL ?= ""
>>> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
>>> +
>>> +export IMAGE_BASENAME = "Beagleboard-demo-image"
>>> +
>>> +DEPENDS = "task-base"
>>> +IMAGE_INSTALL = "\
>>> +    ${XSERVER} \
>>> +    ${ANGSTROM_EXTRA_INSTALL} \
>>> +    task-beagleboard-demo \
>>> +    ${SPLASH} \
>>> +    "
>>> +
>>> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
>>> +
>>> +#zap root password for release images
>>> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
>>> +
>>> +inherit image
>>> --
>>
>> What about a better name? E.g. XM-demo-iimage?
>
> I don't know why we need two demo images.  This should run on Rev Cx as well.

Actually XM-demo-image was just a proposal
For me beagleboard-olddemo-image indicates that it is not really an up
to date version.
I think I would prefer a name that better indicates the purpose. Maybe
add stable in the name?
Another option would be to have the image delivered with the XM as
e.g. beagleboard-demo-image_1.0 and the newer versions e.g. 1.1 etc
(or 2.0 or whatever)
>
>>
>> And to widen the question: do we want to maintain customer/supplier
>> specific images in the oe repo?
>> The company I work for also has some images, but for now we opted to
>> keep them in a private overlay.
>
> I want this to be public and part of the mainline to make it easy for
> people to reproduce.  It is for a relatively broad target.  Is there a
> reason it shouldn't be there?
>

Ok, I understand that (and I have not really a problem with that). It
is just the name that didn't make me too happy.

Frans

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Jason Kridner]

On Tue, Aug 17, 2010 at 5:01 PM, Frans Meulenbroeks
<fransmeulenbroeks@gmail.com> wrote:
> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
>> On Tue, Aug 17, 2010 at 3:54 PM, Frans Meulenbroeks
>> <fransmeulenbroeks@gmail.com> wrote:
>>> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
>>>> I want to use the name beagleboard-demo-image for what actually ships
>>>> with the xM boards.
>>>>
>>>> Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
>>>> ---
>>>>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
>>>>  1 files changed, 30 insertions(+), 0 deletions(-)
>>>>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
>>>>
>>>> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
>>>> new file mode 100644
>>>> index 0000000..d83281c
>>>> --- /dev/null
>>>> +++ b/recipes/images/beagleboard-olddemo-image.bb
>>>> @@ -0,0 +1,30 @@
>>>> +# Demo image for beagleboard
>>>> +
>>>> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
>>>> +
>>>> +XSERVER ?= "xserver-xorg \
>>>> +           xf86-input-evdev \
>>>> +           xf86-input-mouse \
>>>> +           xf86-video-fbdev \
>>>> +           xf86-input-keyboard \
>>>> +"
>>>> +
>>>> +ANGSTROM_EXTRA_INSTALL ?= ""
>>>> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
>>>> +
>>>> +export IMAGE_BASENAME = "Beagleboard-demo-image"
>>>> +
>>>> +DEPENDS = "task-base"
>>>> +IMAGE_INSTALL = "\
>>>> +    ${XSERVER} \
>>>> +    ${ANGSTROM_EXTRA_INSTALL} \
>>>> +    task-beagleboard-demo \
>>>> +    ${SPLASH} \
>>>> +    "
>>>> +
>>>> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
>>>> +
>>>> +#zap root password for release images
>>>> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
>>>> +
>>>> +inherit image
>>>> --
>>>
>>> What about a better name? E.g. XM-demo-iimage?
>>
>> I don't know why we need two demo images.  This should run on Rev Cx as well.
>
> Actually XM-demo-image was just a proposal
> For me beagleboard-olddemo-image indicates that it is not really an up
> to date version.
> I think I would prefer a name that better indicates the purpose. Maybe
> add stable in the name?
> Another option would be to have the image delivered with the XM as
> e.g. beagleboard-demo-image_1.0 and the newer versions e.g. 1.1 etc
> (or 2.0 or whatever)

Koen wanted to keep the old one around--I'm not sure for what purpose.

>>
>>>
>>> And to widen the question: do we want to maintain customer/supplier
>>> specific images in the oe repo?
>>> The company I work for also has some images, but for now we opted to
>>> keep them in a private overlay.
>>
>> I want this to be public and part of the mainline to make it easy for
>> people to reproduce.  It is for a relatively broad target.  Is there a
>> reason it shouldn't be there?
>>
>
> Ok, I understand that (and I have not really a problem with that). It
> is just the name that didn't make me too happy.
>
> Frans
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>

Re: [PATCH] beagleboard-olddemo-image: saved off beagleboard-demo-image

[Paul Menzel]

[-- Attachment #1: Type: text/plain, Size: 2662 bytes --]

Am Dienstag, den 17.08.2010, 23:01 +0200 schrieb Frans Meulenbroeks:
> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
> > On Tue, Aug 17, 2010 at 3:54 PM, Frans Meulenbroeks
> > <fransmeulenbroeks@gmail.com> wrote:
> >> 2010/8/17 Jason Kridner <jkridner@beagleboard.org>:
> >>> I want to use the name beagleboard-demo-image for what actually ships
> >>> with the xM boards.
> >>>
> >>> Signed-off-by: Jason Kridner <jkridner@beagleboard.org>
> >>> ---
> >>>  recipes/images/beagleboard-olddemo-image.bb |   30 +++++++++++++++++++++++++++
> >>>  1 files changed, 30 insertions(+), 0 deletions(-)
> >>>  create mode 100644 recipes/images/beagleboard-olddemo-image.bb
> >>>
> >>> diff --git a/recipes/images/beagleboard-olddemo-image.bb b/recipes/images/beagleboard-olddemo-image.bb
> >>> new file mode 100644
> >>> index 0000000..d83281c
> >>> --- /dev/null
> >>> +++ b/recipes/images/beagleboard-olddemo-image.bb
> >>> @@ -0,0 +1,30 @@
> >>> +# Demo image for beagleboard
> >>> +
> >>> +IMAGE_LINGUAS = "de-de fr-fr en-gb en-us pt-br es-es kn-in ml-in ta-in"
> >>> +
> >>> +XSERVER ?= "xserver-xorg \
> >>> +           xf86-input-evdev \
> >>> +           xf86-input-mouse \
> >>> +           xf86-video-fbdev \
> >>> +           xf86-input-keyboard \
> >>> +"
> >>> +
> >>> +ANGSTROM_EXTRA_INSTALL ?= ""
> >>> +SPLASH = "exquisite exquisite-themes exquisite-theme-angstrom"
> >>> +
> >>> +export IMAGE_BASENAME = "Beagleboard-demo-image"
> >>> +
> >>> +DEPENDS = "task-base"
> >>> +IMAGE_INSTALL = "\
> >>> +    ${XSERVER} \
> >>> +    ${ANGSTROM_EXTRA_INSTALL} \
> >>> +    task-beagleboard-demo \
> >>> +    ${SPLASH} \
> >>> +    "
> >>> +
> >>> +IMAGE_PREPROCESS_COMMAND = "create_etc_timestamp"
> >>> +
> >>> +#zap root password for release images
> >>> +ROOTFS_POSTPROCESS_COMMAND += 'install_linguas; ${@base_conditional("DISTRO_TYPE", "release", "zap_root_password; ", "",d)}'
> >>> +
> >>> +inherit image
> >>> --
> >>
> >> What about a better name? E.g. XM-demo-iimage?
> >
> > I don't know why we need two demo images.  This should run on Rev Cx as well.
> 
> Actually XM-demo-image was just a proposal
> For me beagleboard-olddemo-image indicates that it is not really an up
> to date version.
> I think I would prefer a name that better indicates the purpose. Maybe
> add stable in the name?

So why create an “old” image? What is the difference between these two
images anyway?

> Another option would be to have the image delivered with the XM as
> e.g. beagleboard-demo-image_1.0 and the newer versions e.g. 1.1 etc
> (or 2.0 or whatever)

[…]


Thanks,

Paul

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 205 bytes --]