This patch fixes the case where the EEPROM is programmed but we still use the
fall back case to detect the bone board. Now that EEPROMs are programmed, we should
correctly detect the bone board instead of relying on fall back to bone mode.

PR bumped

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
v2: Resolved merge conflict with 54906ebbec3447b47f298c92772fb619c969ec8a

...Read-name-field-in-EEPROM-header-for-Beag.patch | 28 ++++++++++++++++++++
recipes-bsp/u-boot/u-boot_2011.10rc.bb | 3 +-
2 files changed, 30 insertions(+), 1 deletions(-)
create mode 100644 recipes-bsp/u-boot/u-boot/2011.09git/0005-am335x-evm-Read-name-field-in-EEPROM-header-for-Beag.patch

diff --git a/recipes-bsp/u-boot/u-boot/2011.09git/0005-am335x-evm-Read-name-field-in-EEPROM-header-for-Beag.patch b/recipes-bsp/u-boot/u-boot/2011.09git/0005-am335x-evm-Read-name-field-in-EEPROM-header-for-Beag.patch
new file mode 100644
index 0000000..ef901a9
--- /dev/null
+++ b/recipes-bsp/u-boot/u-boot/2011.09git/0005-am335x-evm-Read-name-field-in-EEPROM-header-for-Beag.patch
@@ -0,0 +1,28 @@
+From 186250ee6abca3f080b5321504a1c5881ffbf7c6 Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes <joelagnel@...>
+Date: Thu, 20 Oct 2011 19:46:53 -0500
+Subject: [PATCH] am335x-evm: Read name field in EEPROM header for BeagleBoard bone detection
+
+Signed-off-by: Joel A Fernandes <joelagnel@...>
+---
+ board/ti/am335x/evm.c | 4 ++++
+ 1 files changed, 4 insertions(+), 0 deletions(-)
+
+diff --git a/board/ti/am335x/evm.c b/board/ti/am335x/evm.c
+index 37e348f..b63dcbe 100755
+--- a/board/ti/am335x/evm.c
++++ b/board/ti/am335x/evm.c
+@@ -501,6 +501,10 @@ int board_init(void)
+ detect_daughter_board_profile();
+ } else if (!strncmp("SKU#03", header.config, 6)) {
+ board_id = IPP_BOARD;
++ } else if (!strncmp("A335BONE", header.name, 8)) {
++ board_id = BONE_BOARD;
++ profile = 1; /* profile 0 is internally considered as 1 */
++ daughter_board_connected = 0;
+ } else {
+ printf("Did not find a recognized configuration, "
+ "assuming BeagleBone\n");
+--
+1.7.1
+
diff --git a/recipes-bsp/u-boot/u-boot_2011.10rc.bb b/recipes-bsp/u-boot/u-boot_2011.10rc.bb
index 0bd39d3..ca7b670 100644
--- a/recipes-bsp/u-boot/u-boot_2011.10rc.bb
+++ b/recipes-bsp/u-boot/u-boot_2011.10rc.bb
@@ -4,7 +4,7 @@ require u-boot.inc
COMPATIBLE_MACHINE = "(ti33x)"
DEFAULT_PREFERENCE_ti33x = "99"
PV = "2011.09+git"
-PR = "r14"
+PR = "r15"

# SPL build
UBOOT_BINARY = "u-boot.img"
@@ -18,6 +18,7 @@ SRC_URI = "git://arago-project.org/git/projects/u-boot-am33x.git;protocol=git;br
file://2011.09git/0001-mach-types-Add-new-beaglebone-machine-type.patch \
file://2011.09git/0003-am335x_evm-single-byte-address-EEPROM-for-board-iden.patch \
file://2011.09git/0004-am335x-evm-fall-back-to-bone-if-header.config-is-emp.patch \
+ file://2011.09git/0005-am335x-evm-Read-name-field-in-EEPROM-header-for-Beag.patch \
"

SRCREV = "9158d7f37d596b867039345cb2e3f8f18f54fe46"
--
1.7.0.4

Applied, thanks!

Please apply these 3 patches which apart from other things also fixes the kernel build and adds EEPROM support.

All changes have been build and runtime tested.

Thanks!

Joel A Fernandes (3):
sdcard_image: Copy uEnv.txt once again as the new bonetester also
checks for GPIO grounding
linux-ti33x-psp 3.1rc8: Update to latest SRCREV, add EEPROM patches
beaglebone-tester: Update to latest and bump PR

classes/sdcard_image.bbclass | 3 +-
...heck-return-value-of-omap_mux_init_signal.patch | 34 ++++++++++
...ility-to-dynamically-reconfigure-chip-inf.patch | 57 +++++++++++++++++
...econfigure-EEPROM-with-new-eeprom_info-in.patch | 65 ++++++++++++++++++++
recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb | 7 ++-
recipes-ti/beagleboard/beaglebone-tester.bb | 6 +-
6 files changed, 165 insertions(+), 7 deletions(-)
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0001-am335x-Check-return-value-of-omap_mux_init_signal.patch
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch

Reverted commit: 6743f427e7fccf9c5f5a262d982da339f69582cf

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
classes/sdcard_image.bbclass | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)

diff --git a/classes/sdcard_image.bbclass b/classes/sdcard_image.bbclass
index 0c9f457..1570d37 100644
--- a/classes/sdcard_image.bbclass
+++ b/classes/sdcard_image.bbclass
@@ -93,8 +93,7 @@ IMAGE_CMD_sdimg () {
suffix=bin
fi

- #cp -v ${IMAGE_ROOTFS}/boot/uEnv.txt ${WORKDIR}/tmp-mnt-boot || true
- cp -v ${IMAGE_ROOTFS}/boot/user.txt ${WORKDIR}/tmp-mnt-boot || true
+ cp -v ${IMAGE_ROOTFS}/boot/{user.txt,uEnv.txt} ${WORKDIR}/tmp-mnt-boot || true

if [ -e ${IMAGE_ROOTFS}/boot/u-boot.$suffix ] ; then
cp -v ${IMAGE_ROOTFS}/boot/{u-boot.$suffix} ${WORKDIR}/tmp-mnt-boot || true
--
1.7.0.4

* Updated to latest SRCREV and bump PR.

Added following patches being submitted to PSP currently:
* EEPROM patches required to get EEPROM working correctly on BBB without
breaking support for EVM.
* omap_mux_init_signal patch to safe guard against incorrectly setting up pinmux.

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
...heck-return-value-of-omap_mux_init_signal.patch | 34 ++++++++++
...ility-to-dynamically-reconfigure-chip-inf.patch | 57 +++++++++++++++++
...econfigure-EEPROM-with-new-eeprom_info-in.patch | 65 ++++++++++++++++++++
recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb | 7 ++-
4 files changed, 161 insertions(+), 2 deletions(-)
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0001-am335x-Check-return-value-of-omap_mux_init_signal.patch
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch
create mode 100644 recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch

diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0001-am335x-Check-return-value-of-omap_mux_init_signal.patch b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0001-am335x-Check-return-value-of-omap_mux_init_signal.patch
new file mode 100644
index 0000000..3ce2df8
--- /dev/null
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0001-am335x-Check-return-value-of-omap_mux_init_signal.patch
@@ -0,0 +1,34 @@
+From b11df2bf8e19b8a4d4e4bb6eae59fde6a1498920 Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes <joelagnel@...>
+Date: Wed, 19 Oct 2011 20:11:00 -0500
+Subject: [PATCH 1/3] am335x: Check return value of omap_mux_init_signal
+
+This helps guard against setting up pin muxmode incorrectly
+
+Signed-off-by: Joel A Fernandes <joelagnel@...>
+---
+ arch/arm/mach-omap2/board-am335xevm.c | 8 +++++---
+ 1 files changed, 5 insertions(+), 3 deletions(-)
+
+diff --git a/arch/arm/mach-omap2/board-am335xevm.c b/arch/arm/mach-omap2/board-am335xevm.c
+index 187f758..f959d95 100644
+--- a/arch/arm/mach-omap2/board-am335xevm.c
++++ b/arch/arm/mach-omap2/board-am335xevm.c
+@@ -590,9 +590,11 @@ static void setup_pin_mux(struct pinmux_config *pin_mux)
+ {
+ int i;
+
+- for (i = 0; pin_mux->string_name != NULL; pin_mux++)
+- omap_mux_init_signal(pin_mux->string_name, pin_mux->val);
+-
++ for (i = 0; pin_mux->string_name != NULL; pin_mux++) {
++ if(omap_mux_init_signal(pin_mux->string_name, pin_mux->val) < 0) {
++ printk(KERN_ERR "Failed to setup pinmux for %s\n", pin_mux->string_name);
++ }
++ }
+ }
+
+ /*
+--
+1.7.4.1
+
diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch
new file mode 100644
index 0000000..5d0d580
--- /dev/null
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch
@@ -0,0 +1,57 @@
+From 8d0697f8962ef52e06012101efdea7713e0e5055 Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes <joelagnel@...>
+Date: Sat, 22 Oct 2011 12:56:44 -0500
+Subject: [PATCH 2/3] at24: Add ability to dynamically reconfigure chip information
+
+As some EEPROMs are used for board name detection, it is not possible to detect
+in advance which EEPROM type is connected without detecting the board first.
+
+In board-a335xevm.c, we use a trial and error approach and this requires for us
+to reconfigure the driver with a new 'eeprom_info' structure different from any
+earlier ones that were passed.
+
+We add new accessor functions to the at24 driver to help with this.
+
+Signed-off-by: Joel A Fernandes <joelagnel@...>
+---
+ drivers/misc/eeprom/at24.c | 11 +++++++++++
+ include/linux/i2c/at24.h | 3 +++
+ 2 files changed, 14 insertions(+), 0 deletions(-)
+
+diff --git a/drivers/misc/eeprom/at24.c b/drivers/misc/eeprom/at24.c
+index ab1ad41..41ebc1f 100644
+--- a/drivers/misc/eeprom/at24.c
++++ b/drivers/misc/eeprom/at24.c
+@@ -456,6 +456,17 @@ static ssize_t at24_macc_write(struct memory_accessor *macc, const char *buf,
+ return at24_write(at24, buf, offset, count);
+ }
+
++struct at24_platform_data *at24_macc_getpdata(struct memory_accessor *macc)
++{
++ struct at24_data *at24 = container_of(macc, struct at24_data, macc);
++ return &at24->chip;
++}
++
++void at24_macc_setpdata(struct memory_accessor *macc, struct at24_platform_data *chip)
++{
++ struct at24_data *at24 = container_of(macc, struct at24_data, macc);
++ at24->chip = *chip;
++}
+ /*-------------------------------------------------------------------------*/
+
+ #ifdef CONFIG_OF
+diff --git a/include/linux/i2c/at24.h b/include/linux/i2c/at24.h
+index 8ace930..7872912 100644
+--- a/include/linux/i2c/at24.h
++++ b/include/linux/i2c/at24.h
+@@ -29,4 +29,7 @@ struct at24_platform_data {
+ void *context;
+ };
+
++struct at24_platform_data *at24_macc_getpdata(struct memory_accessor *macc);
++void at24_macc_setpdata(struct memory_accessor *macc, struct at24_platform_data *chip);
++
+ #endif /* _LINUX_AT24_H */
+--
+1.7.4.1
+
diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch
new file mode 100644
index 0000000..9d3bb6e
--- /dev/null
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch
@@ -0,0 +1,65 @@
+From 18a4a980113f7b290c5694239b0e9b21fb7fe132 Mon Sep 17 00:00:00 2001
+From: Joel A Fernandes <joelagnel@...>
+Date: Sat, 22 Oct 2011 13:03:08 -0500
+Subject: [PATCH 3/3] am335x-evm: Reconfigure EEPROM with new eeprom_info incase of failure
+
+The earlier bone boards have an 8-bit address capable EEPROM with 2kbit size
+and 16 byte page size. This is very different from the EEPROM on the AM335x
+EVM and causes problem when reading for board detection and other purposes.
+
+We first attempt a read with the original EEPROM settings and incase of an
+invalid header, we reconfigure the EEPROM driver with bone_eeprom_info and
+perform a restart of the setup function to reread all EEPROM data again this
+time with the correct EEPROM configuration.
+
+This patch is required to get EEPROM reading working correctly on bone board
+without breaking support for EVM.
+
+Signed-off-by: Joel A Fernandes <joelagnel@...>
+---
+ arch/arm/mach-omap2/board-am335xevm.c | 15 +++++++++++++++
+ 1 files changed, 15 insertions(+), 0 deletions(-)
+
+diff --git a/arch/arm/mach-omap2/board-am335xevm.c b/arch/arm/mach-omap2/board-am335xevm.c
+index f959d95..eb18fb9 100644
+--- a/arch/arm/mach-omap2/board-am335xevm.c
++++ b/arch/arm/mach-omap2/board-am335xevm.c
+@@ -1387,6 +1387,8 @@ static void am335x_setup_daughter_board(struct memory_accessor *m, void *c)
+ }
+ }
+
++static struct at24_platform_data bone_eeprom_info;
++
+ static void am335x_evm_setup(struct memory_accessor *mem_acc, void *context)
+ {
+ int ret;
+@@ -1413,6 +1415,11 @@ static void am335x_evm_setup(struct memory_accessor *mem_acc, void *context)
+ }
+
+ if (config.header != AM335X_EEPROM_HEADER) {
++ if(memcmp(at24_macc_getpdata(mem_acc), &bone_eeprom_info,
++ sizeof(struct at24_platform_data)) != 0) {
++ at24_macc_setpdata(mem_acc, &bone_eeprom_info);
++ return am335x_evm_setup(mem_acc, context);
++ }
+ pr_warning("AM335X: wrong header 0x%x, expected 0x%x\n",
+ config.header, AM335X_EEPROM_HEADER);
+ goto out;
+@@ -1485,6 +1492,14 @@ static struct at24_platform_data am335x_baseboard_eeprom_info = {
+ .context = (void *)NULL,
+ };
+
++static struct at24_platform_data bone_eeprom_info = {
++ .byte_len = (2*1024) / 8,
++ .page_size = 16,
++ .flags = 0x0,
++ .setup = am335x_evm_setup,
++ .context = (void *)NULL,
++};
++
+ /*
+ * Daughter board Detection.
+ * Every board has a ID memory (EEPROM) on board. We probe these devices at
+--
+1.7.4.1
+
diff --git a/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb b/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
index 1c4bee0..bffebea 100644
--- a/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
+++ b/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
@@ -10,8 +10,8 @@ S = "${WORKDIR}/git"
MULTI_CONFIG_BASE_SUFFIX = ""

BRANCH = "master"
-SRCREV = "c7fc664a6a36a4721b43dc287e410a2453f0b782"
-MACHINE_KERNEL_PR_append = "j+gitr${SRCREV}"
+SRCREV = "1955a86594526e18f03c8d62db81119ffc4ccf0f"
+MACHINE_KERNEL_PR_append = "k+gitr${SRCREV}"

COMPATIBLE_MACHINE = "(ti33x)"

@@ -27,6 +27,9 @@ SRC_URI += "git://arago-project.org/git/projects/linux-am33x.git;protocol=git;br
PATCHES_OVER_PSP = " \
file://0001-f_rndis-HACK-around-undefined-variables.patch \
file://0001-am335x-Add-pin-mux-and-init-for-beaglebone-specific-.patch \
+ file://0001-am335x-Check-return-value-of-omap_mux_init_signal.patch \
+ file://0002-at24-Add-ability-to-dynamically-reconfigure-chip-inf.patch \
+ file://0003-am335x-evm-Reconfigure-EEPROM-with-new-eeprom_info-in.patch \
"

SRC_URI += "${@base_contains('DISTRO_FEATURES', 'tipspkernel', "", "${PATCHES_OVER_PSP}", d)}"
--
1.7.0.4

Added:
* PMIC tests
* EEPROM tests
* Memory tests
* GPIO 38 grounding check

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
recipes-ti/beagleboard/beaglebone-tester.bb | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/recipes-ti/beagleboard/beaglebone-tester.bb b/recipes-ti/beagleboard/beaglebone-tester.bb
index 1716122..9e65d65 100644
--- a/recipes-ti/beagleboard/beaglebone-tester.bb
+++ b/recipes-ti/beagleboard/beaglebone-tester.bb
@@ -7,11 +7,11 @@ LIC_FILES_CHKSUM="file://gpl.txt;md5=5b122a36d0f6dc55279a0ebc69f3c60b"
# only scripts and data
inherit allarch

-PR = "r1"
+PR = "r2"

SRC_URI = "git://github.com/joelagnel/validation-scripts.git;protocol=git \
"
-SRCREV = "0806b54c1248b080953402728b0e420243fe844c"
+SRCREV = "fdeaf580e553a0968b777e75306aac3f6a73519e"

S = "${WORKDIR}/git"

@@ -44,7 +44,7 @@ FILES_${PN} += "${base_libdir}/systemd \
/boot \
"

-RDEPENDS_${PN} = "iputils"
+RDEPENDS_${PN} = "iputils memtester"
RRECOMMENDS_${PN} = "kernel-module-g-zero \
kernel-module-g-file-storage \
kernel-module-smsc95xx"
--
1.7.0.4

Op 23 okt. 2011, om 23:27 heeft Fernandes, Joel A het volgende geschreven:

Dear Koen,

In the last update to SRCREV,
http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/commit/?id=ab07a0ea4be961a7e8c7b8b64a56ce6c730cd6e0

The Commit: c7fc664a6a36a4721b43dc287e410a2453f0b782 doesn’t exist anymore in arago. Due to this the fetch breaks.

joel@minted ~/repo/linux-omap-2.6 $ git show c7fc664a6a36a4721b43dc287e410a2453f0b782
fatal: bad object c7fc664a6a36a4721b43dc287e410a2453f0b782

Either the Arago tree was rebased or the commit ID is not valid.

It was rebased:

commit c7fc664a6a36a4721b43dc287e410a2453f0b782
Author: Ajay Kumar Gupta <ajay.gupta@...>
Date: Fri Oct 21 14:18:25 2011 +0530

am335xevm: defconfig: usb setup

Made one gadget (DBGP) as builtin for USB1 port and other gadget driver as
modules for USB0 port.

commit 7a68182e84ec58909a31a37d3c21619ed8ab2111
Author: Ajay Kumar Gupta <ajay.gupta@...>
Date: Fri Oct 21 10:32:12 2011 +0530

usb: ether_gadget: fix insmod panic after fsg rmmod

Fixes kernel panic seen during g_ether.ko module insertion performed
after the FSG gadget rmmod.

Ether gadget doesn't reset the usb_ep(s) during initialization and
so was getting the previous gadget's usb_ep->desc data.

commit 4be081bbeab0973ae2021622af828be215a3c0ca
Author: Ravi B <ravibabu@...>
Date: Wed Oct 19 21:26:55 2011 +0530

usb: am335x: gadget: add option for dbgp as one builtin gadget

DBGP is added as only gadget option to be selected for a port as
builtin driver. The gadget driver for other ports can be compiled
as module and inserted after the bootups.

Op 24 okt. 2011, om 05:59 heeft Joel A Fernandes het volgende geschreven:

Please apply these 3 patches which apart from other things also fixes the kernel build and adds EEPROM support.

All changes have been build and runtime tested.

Thanks!

Joel A Fernandes (3):
sdcard_image: Copy uEnv.txt once again as the new bonetester also
checks for GPIO grounding
linux-ti33x-psp 3.1rc8: Update to latest SRCREV, add EEPROM patches
beaglebone-tester: Update to latest and bump PR

I did the uEnv change a bit different, but in the end all the above changes are in.

regards,

Koen

Koen,

Am 21.10.2011 11:14, schrieb Koen Kooi:

I'm currently trying to build an image for the TI 8148 EVM board. For
that I added the meta-ti layer to the standard Yocto/Edison environment.

Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

Yocto/Poky lacks support for various meta-ti (and OE-classic) constructs needed for a successfull build. Following the instructions above you will get a proper setup.

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

Regards
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@...

Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html

Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:

Koen,

Am 21.10.2011 11:14, schrieb Koen Kooi:

I'm currently trying to build an image for the TI 8148 EVM board. For
that I added the meta-ti layer to the standard Yocto/Edison environment.

Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

Yocto/Poky lacks support for various meta-ti (and OE-classic) constructs needed for a successfull build. Following the instructions above you will get a proper setup.

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:

OE Build Configuration:
BB_VERSION = "1.13.3"
TARGET_ARCH = "arm"
TARGET_OS = "linux-gnueabi"
MACHINE = "dm814x-evm"
DISTRO = "angstrom"
DISTRO_VERSION = "v2011.10-core"
TUNE_FEATURES = "armv7a vfp neon cortexa8"
TARGET_FPU = "vfp-neon"
meta-angstrom = "master:14f73c63403525f85a15f61f88895ba377364338"
meta-oe
meta-efl
meta-gpe
meta-gnome
meta-xfce = "master:5da48e6e4a4ab0488943c5e93f005211bd7a22f7"
meta-ti = "master:2ea9f93740259be7eee59edeb88e632c5441fb58"
meta-ettus = "master:617506b5cfd2b8325d85f0dcba0232c3f796d044"
meta-efikamx = "master:2ef47fdd4e8232d766c0c63d9427253ee56e31d0"
meta-nslu2 = "master:17853811179f2760791c6b138f96e9dd15493517"
meta-htc
meta-nokia
meta-openmoko
meta-palm = "oe-core:794b32d234dbf7e6626c8a0efc915fc04804b9d0"
meta-sugarbay
meta-crownbay
meta-emenlow
meta-fishriver
meta-jasperforest
meta-n450 = "master:0ea04b02119c44865e5e1c2529c74950928c3347"
meta = "master:99da9a4e65f9dffb04efc3ad60125194c476d6b3"

Could you please share your version of that so we can see if there are fixes missing?

regards,

Koen

Koen,
Am 24.10.2011 10:58, schrieb Koen Kooi:

Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:

Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:

Could you please share your version of that so we can see if there are fixes missing?

Difficult at the moment because now I'm back to work and the data is at
home. :-) But I will setup this again on my work machine and see that I
get the firewall-issues solved, so I should be able to reproduce my
results.

I was really just following the linked instructions above, maybe I
should have setup something in my local.conf...?

Regards
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@...

Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html

Op 24 okt. 2011, om 11:05 heeft Rainer Koenig het volgende geschreven:

Koen,
Am 24.10.2011 10:58, schrieb Koen Kooi:

Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:

Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:

Could you please share your version of that so we can see if there are fixes missing?

Difficult at the moment because now I'm back to work and the data is at
home. :-) But I will setup this again on my work machine and see that I
get the firewall-issues solved, so I should be able to reproduce my
results.

The oebb.sh script has builtin firewall support, have a look at that. If something is missing, please let us know.

I was really just following the linked instructions above, maybe I
should have setup something in my local.conf...?

No, the setup scripts try really hard to avoid having you edit conf files :)

regards,

Koen

Op 24 okt. 2011, om 11:05 heeft Rainer Koenig het volgende geschreven:

Koen,
Am 24.10.2011 10:58, schrieb Koen Kooi:

Op 24 okt. 2011, om 10:48 heeft Rainer Koenig het volgende geschreven:

Please follow the instructions detailed in the meta-ti README: http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:

Could you please share your version of that so we can see if there are fixes missing?

Difficult at the moment because now I'm back to work and the data is at
home. :-) But I will setup this again on my work machine and see that I
get the firewall-issues solved, so I should be able to reproduce my
results.

Roger provided a log with a related looking bug, which should get solved Real Soon(TM) when the following gets applied:

http://patchwork.openembedded.org/patch/13783/

In the mean time you should be able to get around it by doing 'bitbake mesa-dri' manually.

regards,

Koen

On Mon, Oct 24, 2011 at 01:22:54PM +0200, Koen Kooi wrote:

Op 24 okt. 2011, om 11:05 heeft Rainer Koenig het volgende geschreven:

Koen,
Am 24.10.2011 10:58, schrieb Koen Kooi:

Tried this over the weekend on my home PC. Yes, works. But I was just
able to build a console image. The build of systemd-gnome-image fails
with the error that nothing provides "DRI". MACHINE=dm8148-evm.

I'm not seeing that with this set of metadata:
Could you please share your version of that so we can see if there are
fixes missing?

Difficult at the moment because now I'm back to work and the data is at
home. :-) But I will setup this again on my work machine and see that I
get the firewall-issues solved, so I should be able to reproduce my
results.

Roger provided a log with a related looking bug, which should get solved
Real Soon(TM) when the following gets applied:

http://patchwork.openembedded.org/patch/13783/

In the mean time you should be able to get around it by doing 'bitbake
mesa-dri' manually.

Yep, I can confirm this issue. I had it fixed locally by adding mesa-dri to
DEPENDS in xorg-xserver... Didn't have time to submit either a patch or a
bugreport though.

--
Denys

Am 24.10.2011 20:37, schrieb Denys Dmytriyenko:

In the mean time you should be able to get around it by doing 'bitbake
mesa-dri' manually.

Yep, I can confirm this issue. I had it fixed locally by adding mesa-dri to
DEPENDS in xorg-xserver... Didn't have time to submit either a patch or a
bugreport though.

Ok, with all the hints from this thread I was able to build an image.
Testing on my DM8148 EVM wasn't that much of a success, image boots to
console, but is lacking of the required (question: what do I need for
this EVM, anyone from TI can tell me?) xorg-modules. /etc/X11/xorg.conf
tries to load an intel driver which is definitely out of range for this
board. :-)

How can I see from the logs what xserver/xorg-components were built and
how can I add the missing ones?

TIA
Rainer
--
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax: +49-821-804-2131
Mail: mailto:Rainer.Koenig@...

Internet ts.fujtsu.com
Company Details ts.fujitsu.com/imprint.html

Op 25 okt 2011, om 14:32 heeft Rainer Koenig het volgende geschreven:

Am 24.10.2011 20:37, schrieb Denys Dmytriyenko:

In the mean time you should be able to get around it by doing 'bitbake
mesa-dri' manually.

Yep, I can confirm this issue. I had it fixed locally by adding mesa-dri to
DEPENDS in xorg-xserver... Didn't have time to submit either a patch or a
bugreport though.

Ok, with all the hints from this thread I was able to build an image.
Testing on my DM8148 EVM wasn't that much of a success, image boots to
console, but is lacking of the required (question: what do I need for
this EVM, anyone from TI can tell me?) xorg-modules. /etc/X11/ xorg.conf
tries to load an intel driver which is definitely out of range for this
board. :-)

How can I see from the logs what xserver/xorg-components were built and
how can I add the missing ones?

You need to ask your TI rep for a m3 firmware file. When you have that you need to build some syslink things to get your display working. I integrated it all a few months ago for a demo you probably have seen :)

I'm at a conference now, so I can't look up my notes for the exact sequence, but it starts with getting the magic firmware file.

regards,

Koen

Enable the PL2303 usb-to-serial driver required for serial output
from the beaglebone tester.

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
.../linux-ti33x-psp-3.0+3.1rc/beaglebone/defconfig | 3 ++-
recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/beaglebone/defconfig b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/beaglebone/defconfig
index 4b3c21d..478ec3e 100644
--- a/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/beaglebone/defconfig
+++ b/recipes-kernel/linux/linux-ti33x-psp-3.0+3.1rc/beaglebone/defconfig
@@ -2558,7 +2558,8 @@ CONFIG_USB_LIBUSUAL=y
# USB port drivers
#
# CONFIG_USB_USS720 is not set
-# CONFIG_USB_SERIAL is not set
+CONFIG_USB_SERIAL=y
+CONFIG_USB_SERIAL_PL2303=y

#
# USB Miscellaneous drivers
diff --git a/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb b/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
index bffebea..fbee01f 100644
--- a/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
+++ b/recipes-kernel/linux/linux-ti33x-psp_3.0+3.1rc.bb
@@ -11,7 +11,7 @@ MULTI_CONFIG_BASE_SUFFIX = ""

BRANCH = "master"
SRCREV = "1955a86594526e18f03c8d62db81119ffc4ccf0f"
-MACHINE_KERNEL_PR_append = "k+gitr${SRCREV}"
+MACHINE_KERNEL_PR_append = "l+gitr${SRCREV}"

COMPATIBLE_MACHINE = "(ti33x)"

--
1.7.0.4

Added:
- Output test status to USB serial port
- Made more verbose

Signed-off-by: Joel A Fernandes <joelagnel@...>
---
recipes-ti/beagleboard/beaglebone-tester.bb | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-ti/beagleboard/beaglebone-tester.bb b/recipes-ti/beagleboard/beaglebone-tester.bb
index 9e65d65..9e49e87 100644
--- a/recipes-ti/beagleboard/beaglebone-tester.bb
+++ b/recipes-ti/beagleboard/beaglebone-tester.bb
@@ -7,11 +7,11 @@ LIC_FILES_CHKSUM="file://gpl.txt;md5=5b122a36d0f6dc55279a0ebc69f3c60b"
# only scripts and data
inherit allarch

-PR = "r2"
+PR = "r3"

SRC_URI = "git://github.com/joelagnel/validation-scripts.git;protocol=git \
"
-SRCREV = "fdeaf580e553a0968b777e75306aac3f6a73519e"
+SRCREV = "c6faf47c9e73da7d256cd226bc9eb2a3e4a19aaa"

S = "${WORKDIR}/git"

--
1.7.0.4