* ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 12:33 Thilo Fromm
2012-05-18 12:51 ` Koen Kooi
0 siblings, 1 reply; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 12:33 UTC (permalink / raw)
To: openembedded-devel, meta-ti
Hello *.*,
sorry for the cross-post (openembedded-devel, meta-ti), I think this
affects both projects one way or the other.
Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This
means with oe-core + meta-oe you now can choose between gcc-4.6 and
gcc-4.7. However, both compilers break the kernel we're using
(ti81xx-psp-linux-2.6.37).
Firstly, it is necessary to add the compiler flag
"-mno-unaligned-access" to the kernel build, or else the kernel would
not boot at all[1]. After adding this flag (e.g. by setting '
KERNEL_CC_append += "-mno-unaligned-access " ' in the kernel recipe)
the kernel boots but fails with a NULL pointer access before it
reaches user space (see boot log at [2]).
With the departure of gcc-4.5 there's currently no way to build a
working kernel for a TI dm81xx system.
Steps to reproduce the issue:
0. First you'll need a ti8148-evm board to test the kernel on
1. check out our layer configuration:
git clone git://github.com/DFE/HidaV.git; cd HidaV
2. get the other layers, init build env:
. ./hidav-init .
3. disable gcc-4.5 for the build:
sed -i -e 's/^ANGSTROM_GCC_VERSION/# ANGSTROM_GCC_VERSION/'
meta-hidav/conf/machine/hidav.conf
4. build the kernel:
bitbake virtual/linux
5. Boot the kernel on your ti8148-evm evaluation board; see it crash
Just to stress my point once more: we currently have no way to build a
sane kernel for TI 8148 based systems with latest oe-core, meta-oe,
and Angstrom.
Regards,
Thilo
Appendix
--------------
[1] <http://git.freesmartphone.org/?p=linux-2.6.git;a=commit;h=78ffc81db8911acdabd026ad3fdefa20b4e34e52>
[2] Faulty Kernel Boot Log:
---------- SNIPP ----------
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Linux version 2.6.37
(maniac@bfg9000.internal.dresearch-fe.de) (gcc version 4.6.4 20120303
(prerelease) (GCC) ) #2 Fri May 18 13:10:18 CEST 2012
[ 0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
[ 0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine: ti8148evm
[ 0.000000] vram size = 52428800 at 0x0
[ 0.000000] reserved size = 52428800 at 0x0
[ 0.000000] FB: Reserving 52428800 bytes SDRAM for VRAM
[ 0.000000] Memory policy: ECC disabled, Data cache writeback
[ 0.000000] OMAP chip is TI8148 2.0
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on.
Total pages: 247296
[ 0.000000] Kernel command line: console=ttyO0,115200n8 rootwait
root=/dev/mmcblk0p2 ro rootfstype=ext4 mem=1024M earlyprink vram=50M
ip=off noinitrd user_debug=255 systemd.log_target=kmsg
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 974MB = 974MB total
[ 0.000000] Memory: 982772k/982772k available, 65804k reserved,
210944K highmem
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
[ 0.000000] DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
[ 0.000000] vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
[ 0.000000] pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
[ 0.000000] modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
[ 0.000000] .init : 0xc0008000 - 0xc0052000 ( 296 kB)
[ 0.000000] .text : 0xc0052000 - 0xc04d2000 (4608 kB)
[ 0.000000] .data : 0xc04d2000 - 0xc05154e0 ( 270 kB)
[ 0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0,
CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:407
[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with
128 interrupts
[ 0.000000] Total of 128 interrupts on 1 active controller
[ 0.000000] GPMC revision 6.0
[ 0.000000] Trying to install interrupt handler for IRQ400
[ 0.000000] Trying to install interrupt handler for IRQ401
[ 0.000000] Trying to install interrupt handler for IRQ402
[ 0.000000] Trying to install interrupt handler for IRQ403
[ 0.000000] Trying to install interrupt handler for IRQ404
[ 0.000000] Trying to install interrupt handler for IRQ405
[ 0.000000] Trying to install interrupt handler for IRQ406
[ 0.000000] Trying to install type control for IRQ407
[ 0.000000] Trying to set irq flags for IRQ407
[ 0.000000] OMAP clockevent source: GPTIMER1 at 20000000 Hz
[ 0.000000] Console: colour dummy device 80x30
[ 0.000000] Calibrating delay loop... 598.01 BogoMIPS (lpj=2990080)
[ 0.220000] pid_max: default: 32768 minimum: 301
[ 0.230000] Security Framework initialized
[ 0.230000] Mount-cache hash table entries: 512
[ 0.230000] CPU: Testing write buffer coherency: ok
[ 0.230000] ftrace: allocating 14049 entries in 42 pages
[ 0.240000] devtmpfs: initialized
[ 0.250000] omap_voltage_early_init: voltage driver support not added
[ 0.250000] regulator: core version 0.5
[ 0.250000] regulator: dummy:
[ 0.250000] NET: Registered protocol family 16
[ 0.250000] OMAP GPIO hardware version 0.1
[ 0.250000] OMAP GPIO hardware version 0.1
[ 0.250000] OMAP GPIO hardware version 0.1
[ 0.250000] OMAP GPIO hardware version 0.1
[ 0.260000] omap_mux_init: Add partition: #1: core, flags: 4
[ 0.270000] registered ti814x_vpss device
[ 0.270000] registered TI814x on-chip HDMI device
[ 0.280000] registered ti81xx_vidout device
[ 0.290000] Debugfs: Only enabling/disabling deep sleep and wakeup
timer is supported now
[ 0.290000] ti81xx_pcie: Invoking PCI BIOS...
[ 0.290000] ti81xx_pcie: Setting up Host Controller...
[ 0.290000] ti81xx_pcie: Register base mapped @0xf0820000
[ 0.400000] ti81xx_pcie: Starting PCI scan...
[ 0.400000] PCI: bus0: Fast back to back transfers enabled
[ 0.410000] bio: create slab <bio-0> at 0
[ 0.410000] vgaarb: loaded
[ 0.410000] SCSI subsystem initialized
[ 0.420000] usbcore: registered new interface driver usbfs
[ 0.420000] usbcore: registered new interface driver hub
[ 0.420000] usbcore: registered new device driver usb
[ 0.420000] registerd cppi-dma Intr @ IRQ 17
[ 0.420000] Cppi41 Init Done
[ 0.420000] omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
[ 0.420000] pcf857x 1-0021: gpios 128..143 on a pcf8575
[ 0.420000] omap_i2c omap_i2c.3: bus 3 rev4.0 at 100 kHz
[ 0.430000] Switching to clocksource gp timer
[ 0.490000] musb-hdrc: version 6.0, host, debug=0
[ 0.500000] musb-hdrc musb-hdrc.0: dma type: dma-cppi41
[ 0.500000] musb-hdrc musb-hdrc.0: MUSB HDRC host driver
[ 0.500000] musb-hdrc musb-hdrc.0: new USB bus registered, assigned
bus number 1
[ 0.500000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.500000] usb usb1: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 0.500000] usb usb1: Product: MUSB HDRC host driver
[ 0.500000] usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
[ 0.500000] usb usb1: SerialNumber: musb-hdrc.0
[ 0.500000] hub 1-0:1.0: USB hub found
[ 0.500000] hub 1-0:1.0: 1 port detected
[ 0.500000] musb-hdrc musb-hdrc.0: USB Host mode controller at
f081e000 using DMA, IRQ 18
[ 0.500000] musb-hdrc musb-hdrc.1: dma type: dma-cppi41
[ 0.500000] musb-hdrc musb-hdrc.1: MUSB HDRC host driver
[ 0.500000] musb-hdrc musb-hdrc.1: new USB bus registered, assigned
bus number 2
[ 0.500000] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.500000] usb usb2: New USB device strings: Mfr=3, Product=2,
SerialNumber=1
[ 0.500000] usb usb2: Product: MUSB HDRC host driver
[ 0.500000] usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
[ 0.500000] usb usb2: SerialNumber: musb-hdrc.1
[ 0.500000] hub 2-0:1.0: USB hub found
[ 0.500000] hub 2-0:1.0: 1 port detected
[ 0.510000] musb-hdrc musb-hdrc.1: USB Host mode controller at
f0826800 using DMA, IRQ 19
[ 0.510000] NET: Registered protocol family 2
[ 0.510000] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.510000] TCP established hash table entries: 131072 (order: 8,
1048576 bytes)
[ 0.510000] TCP bind hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.510000] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.510000] TCP reno registered
[ 0.510000] UDP hash table entries: 512 (order: 1, 8192 bytes)
[ 0.510000] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[ 0.510000] NET: Registered protocol family 1
[ 0.510000] PMU: registered new PMU device of type 0
[ 0.510000] omap-iommu omap-iommu.0: ducati registered
[ 0.510000] omap-iommu omap-iommu.1: sys registered
[ 0.610000] highmem bounce pool size: 64 pages
[ 0.630000] VFS: Disk quotas dquot_6.5.2
[ 0.630000] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.640000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.640000] aufs 2.2-standalone.tree-37-20120326
[ 0.640000] msgmni has been set to 1507
[ 0.640000] Block layer SCSI generic (bsg) driver version 0.4
loaded (major 253)
[ 0.640000] io scheduler noop registered
[ 0.640000] io scheduler deadline registered
[ 0.640000] io scheduler cfq registered (default)
[ 0.640000] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[ 0.650000] omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
[ 1.360000] console [ttyO0] enabled
[ 1.370000] omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
[ 1.380000] omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
[ 1.380000] omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
[ 1.390000] omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
[ 1.400000] omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
[ 1.430000] brd: module loaded
[ 1.450000] loop: module loaded
[ 1.450000] ahci ahci.0: forcing PORTS_IMPL to 0x1
[ 1.460000] ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1
impl platform mode
[ 1.460000] ahci ahci.0: flags: ncq sntf pm led clo only pmp pio
slum part ccc apst
[ 1.480000] scsi0 : ahci_platform
[ 1.480000] ata1: SATA max UDMA/133 mmio [mem
0x4a140000-0x4a150fff] port 0x100 irq 16
[ 1.490000] omap2-nand driver initializing
[ 1.490000] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xcc (Micron )
[ 1.500000] Creating 7 MTD partitions on "omap2-nand.0":
[ 1.510000] 0x000000000000-0x000000100000 : "bootloader"
[ 1.520000] 0x000000100000-0x000000200000 : "bootconfig"
[ 1.530000] 0x000000200000-0x000000c00000 : "kernel1"
[ 1.540000] blockrom0: 1024 KiB; EBs 8 user, 0 spare,
0 mgmt, 0 bad, 8 toal
[ 1.550000] blockrom1: 1024 KiB; EBs 8 user, 0 spare,
0 mgmt, 0 bad, 8 toal
[ 1.570000] 0x000000c00000-0x000001600000 : "kernel2"
[ 1.580000] 0x000001600000-0x000007a00000 : "rootfs1"
[ 1.630000] blockrom3: 10240 KiB; EBs 80 user, 0 spare,
0 mgmt, 0 bad, 80 toal
[ 1.650000] blockrom2: 10240 KiB; EBs 80 user, 0 spare,
0 mgmt, 0 bad, 80 toal
[ 1.700000] 0x000007a00000-0x00000de00000 : "rootfs2"
[ 1.750000] blockrom4: 102272 KiB; EBs 799 user, 0 spare,
0 mgmt, 1 bad, 800 toal
[ 1.800000] blockrom5: 101760 KiB; EBs 795 user, 0 spare,
0 mgmt, 5 bad, 800 toal
[ 1.810000] 0x00000de00000-0x000020000000 : "application_fs"
[ 1.940000] ata1: SATA link down (SStatus 0 SControl 300)
[ 2.070000] blockrom6: 295296 KiB; EBs 2307 user, 0 spare,
0 mgmt, 13 bad, 2320 toal
[ 2.120000] davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
[ 2.120000] davinci_mdio davinci_mdio.0: detected phy mask fffffffc
[ 2.130000] davinci_mdio.0: probed
[ 2.130000] davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
[ 2.140000] davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
[ 2.150000] usbcore: registered new interface driver cdc_ether
[ 2.160000] usbcore: registered new interface driver dm9601
[ 2.160000] usbcore: registered new interface driver cdc_acm
[ 2.170000] cdc_acm: v0.26:USB Abstract Control Model driver for
USB modems and ISDN adapters
[ 2.180000] Initializing USB Mass Storage driver...
[ 2.180000] usbcore: registered new interface driver usb-storage
[ 2.190000] USB Mass Storage support registered.
[ 2.190000] mice: PS/2 mouse device common for all mice
[ 2.420000] qt602240_ts 1-004a: Family ID: 128 Variant ID: 1
Version: 22 Build: 171
[ 2.430000] qt602240_ts 1-004a: Matrix X Size: 18 Matrix Y Size: 12
Object Num: 17
[ 2.440000] input: AT42QT602240/ATMXT224 Touchscreen as
/devices/platform/omap/omap_i2c.1/i2c-1/1-004a/input/input0
[ 2.450000] omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
[ 2.460000] i2c /dev entries driver
[ 2.460000] OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
[ 2.470000] usbcore: registered new interface driver usbhid
[ 2.480000] usbhid: USB HID core driver
[ 2.480000] Unable to handle kernel NULL pointer dereference at
virtual address 00000002
[ 2.490000] pgd = c0004000
[ 2.490000] [00000002] *pgd=00000000
[ 2.500000] Internal error: Oops: 5 [#1]
[ 2.500000] last sysfs file:
[ 2.500000] Modules linked in:
[ 2.500000] CPU: 0 Not tainted (2.6.37 #2)
[ 2.500000] PC is at strcmp+0xc/0x40
[ 2.500000] LR is at omap_mbox_get+0x44/0x1d8
[ 2.500000] pc : [<c0212b6c>] lr : [<c00784ec>] psr: a0000013
[ 2.500000] sp : ef85bef8 ip : ef85bf08 fp : ef85bf04
[ 2.500000] r10: c03246f4 r9 : 00000000 r8 : 00000040
[ 2.500000] r7 : ef85bf44 r6 : c046bc75 r5 : c050ba68 r4 : c04e8d14
[ 2.500000] r3 : 00000064 r2 : 00000076 r1 : c046bc75 r0 : 00000002
[ 2.500000] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM
Segment kernel
[ 2.500000] Control: 10c5387d Table: 80004019 DAC: 00000017
[ 2.500000] Process swapper (pid: 1, stack limit = 0xef85a2e8)
[ 2.500000] Stack: (0xef85bef8 to 0xef85c000)
[ 2.500000] bee0:
ef85bf2c ef85bf08
[ 2.500000] bf00: c00784ec c0212b6c c0320944 c0212b6c 00000000
c050ba0c c050ba08 00000000
[ 2.500000] bf20: ef85bf74 ef85bf30 c0324854 c00784b4 00000000
00000000 00000020 ffffffff
[ 2.500000] bf40: 00000001 00000000 00000000 c002ec58 c00285c8
00000000 00000013 00000000
[ 2.500000] bf60: 00000000 00000000 ef85bfa4 ef85bf78 c0028604
c0324650 ef85a000 c002ec58
[ 2.500000] bf80: c00285c8 00000000 00000013 00000000 00000000
00000000 ef85bfdc ef85bfa8
[ 2.500000] bfa0: c0052450 c00285d4 ef85bfc4 00000196 c04f5904
c00c07d0 c002ec58 c002ecdc
[ 2.500000] bfc0: c00841cc 00000013 00000000 00000000 ef85bff4
ef85bfe0 c0008d20 c0052394
[ 2.500000] bfe0: 00000000 c0008c80 00000000 ef85bff8 c00841cc
c0008c8c 69782969 7979f961
[ 2.500000] Backtrace:
[ 2.500000] [<c0212b60>] (strcmp+0x0/0x40) from [<c00784ec>]
(omap_mbox_get+0x44/0x1d8)
[ 2.500000] [<c00784a8>] (omap_mbox_get+0x0/0x1d8) from
[<c0324854>] (notify_shm_drv_setup+0x210/0x2f0)
[ 2.500000] r6:00000000 r5:c050ba08 r4:c050ba0c
[ 2.500000] [<c0324644>] (notify_shm_drv_setup+0x0/0x2f0) from
[<c0028604>] (notify_init+0x3c/0x2b0)
[ 2.500000] [<c00285c8>] (notify_init+0x0/0x2b0) from [<c0052450>]
(do_one_initcall+0xc8/0x1a0)
[ 2.500000] [<c0052388>] (do_one_initcall+0x0/0x1a0) from
[<c0008d20>] (kernel_init+0xa0/0x14c)
[ 2.500000] r9:00000000 r8:00000000 r7:00000013 r6:c00841cc r5:c002ecdc
[ 2.500000] r4:c002ec58
[ 2.500000] [<c0008c80>] (kernel_init+0x0/0x14c) from [<c00841cc>]
(do_exit+0x0/0x658)
[ 2.500000] r5:c0008c80 r4:00000000
[ 2.500000] Code: e89da800 e1a0c00d e92dd800 e24cb004 (e4d03001)
[ 2.730000] ---[ end trace ffdc45ac5a6696b9 ]---
[ 2.740000] Kernel panic - not syncing: Attempted to kill init!
[ 2.750000] Backtrace:
[ 2.750000] [<c005ad34>] (dump_backtrace+0x0/0x118) from
[<c03a5014>] (dump_stack+0x20/0x24)
[ 2.760000] r6:ef85a000 r5:c04ec558 r4:c0515ce0 r3:07730fa7
[ 2.760000] [<c03a4ff4>] (dump_stack+0x0/0x24) from [<c03a522c>]
(panic+0x64/0x184)
[ 2.770000] [<c03a51c8>] (panic+0x0/0x184) from [<c008423c>]
(do_exit+0x70/0x658)
[ 2.780000] r3:c04ec558 r2:ef85bd18 r1:0000002e r0:c046e2e2
[ 2.780000] r7:ef85c000
[ 2.790000] [<c00841cc>] (do_exit+0x0/0x658) from [<c005b25c>]
(die+0x1a4/0x1d0)
[ 2.790000] r7:00000001
[ 2.800000] [<c005b0b8>] (die+0x0/0x1d0) from [<c03a507c>]
(__do_kernel_fault.part.1+0x64/0x84)
[ 2.810000] r8:00000005 r7:ef85beb0 r6:00000000 r5:00000005 r4:00000002
[ 2.810000] [<c03a5018>] (__do_kernel_fault.part.1+0x0/0x84) from
[<c03ac66c>] (do_page_fault+0x204/0x220)
[ 2.820000] r7:00000000 r3:ef85beb0
[ 2.830000] [<c03ac468>] (do_page_fault+0x0/0x220) from
[<c03ac6b4>] (do_translation_fault+0x2c/0xb0)
[ 2.840000] [<c03ac688>] (do_translation_fault+0x0/0xb0) from
[<c0052278>] (do_DataAbort+0x44/0xa8)
[ 2.850000] r7:ef85beb0 r6:00000002 r5:c04d6510 r4:00000005
[ 2.850000] [<c0052234>] (do_DataAbort+0x0/0xa8) from [<c03aa56c>]
(__dabt_svc+0x4c/0x60)
[ 2.860000] Exception stack(0xef85beb0 to 0xef85bef8)
[ 2.870000] bea0: 00000002
c046bc75 00000076 00000064
[ 2.870000] bec0: c04e8d14 c050ba68 c046bc75 ef85bf44 00000040
00000000 c03246f4 ef85bf04
[ 2.880000] bee0: ef85bf08 ef85bef8 c00784ec c0212b6c a0000013 ffffffff
[ 2.890000] r7:ef85bf44 r6:c046bc75 r5:ef85bee4 r4:ffffffff
[ 2.900000] [<c0212b60>] (strcmp+0x0/0x40) from [<c00784ec>]
(omap_mbox_get+0x44/0x1d8)
[ 2.900000] [<c00784a8>] (omap_mbox_get+0x0/0x1d8) from
[<c0324854>] (notify_shm_drv_setup+0x210/0x2f0)
[ 2.910000] r6:00000000 r5:c050ba08 r4:c050ba0c
[ 2.920000] [<c0324644>] (notify_shm_drv_setup+0x0/0x2f0) from
[<c0028604>] (notify_init+0x3c/0x2b0)
[ 2.930000] [<c00285c8>] (notify_init+0x0/0x2b0) from [<c0052450>]
(do_one_initcall+0xc8/0x1a0)
[ 2.940000] [<c0052388>] (do_one_initcall+0x0/0x1a0) from
[<c0008d20>] (kernel_init+0xa0/0x14c)
[ 2.950000] r9:00000000 r8:00000000 r7:00000013 r6:c00841cc r5:c002ecdc
[ 2.950000] r4:c002ec58
[ 2.960000] [<c0008c80>] (kernel_init+0x0/0x14c) from [<c00841cc>]
(do_exit+0x0/0x658)
[ 2.970000] r5:c0008c80 r4:00000000
---------- SNIPP ----------
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread* Re: ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 12:33 ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5 Thilo Fromm
@ 2012-05-18 12:51 ` Koen Kooi
0 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 12:51 UTC (permalink / raw)
To: openembedded-devel; +Cc: meta-ti
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 18-05-12 14:33, Thilo Fromm schreef:
> Hello *.*,
>
> sorry for the cross-post (openembedded-devel, meta-ti), I think this
> affects both projects one way or the other.
>
> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
> However, both compilers break the kernel we're using
> (ti81xx-psp-linux-2.6.37).
What happens when you disable the mailbox? AIUI you shouldn't need that on
Ne/Ce.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPtkXQAAoJEHZqAkdh1vT6SYsQAJndlj4m7rIuuQdsseJYZBDj
C2E/fXa6GkZmZNMWEBmZvdlNlw0C4phg8lGKYFzoL+DPPL4/TrvkZ6h1QU/uHUiU
a0L41O9jI6HsnQ/dS7OzG7V+Gcgduv0gUvdc0wK+km2BtBtnR7nG4501hGd//xjZ
D4XN+WpBsr6PL7XawXyg0cHDEbBvq/yHqy3mTkBW9/d5EdAlWjVTuj6FhaMouZQr
fBIiEAlWl0iZsxa8VbVBFvZHJcAyS5rut1KINO7yXgdZ0Pa58nppJJ8P3DSJ8WkP
vQzvQ6GRuU/0FdKRS/gvvQak1kEa+2vHM3y911ivlppPAdqXu6CszqMi5H5GmI27
4JGq0MJ5h9xltz7+k3EpmriztRHnqoFyG9a4cI8NR5aTtHLc5GzXJBPQ7xKbvf2M
xY/qy9pEtCw6SbKO9I6+oEruVS1UOl9LAG7ATFItWGm0dHw7HXp0EpNhwmo2Si5n
Yc1OdBasCOxA7yRBxzvEtSNfeY0BiDniIAtuWpFVQ/sUY3ao+Aiz+9ATRYSXtBKb
HtXP9pMGM9Oa9L0SADXsQbopt7M8rkgLXD6DkLBq/LMenqp5vkMP8WBqBl45g1yG
8n8EBmohylFP+L0kSI7oHr7+zJu7EZnpUP2jsHR9+8coBTia1zfvrLSq2wZV8W/d
WAFvJzJKWbhrNxzLYLyh
=+Key
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 12:51 ` Koen Kooi
0 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 12:51 UTC (permalink / raw)
To: meta-ti; +Cc: openembedded-devel
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Op 18-05-12 14:33, Thilo Fromm schreef:
> Hello *.*,
>
> sorry for the cross-post (openembedded-devel, meta-ti), I think this
> affects both projects one way or the other.
>
> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
> However, both compilers break the kernel we're using
> (ti81xx-psp-linux-2.6.37).
What happens when you disable the mailbox? AIUI you shouldn't need that on
Ne/Ce.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org
iQIcBAEBAgAGBQJPtkXQAAoJEHZqAkdh1vT6SYsQAJndlj4m7rIuuQdsseJYZBDj
C2E/fXa6GkZmZNMWEBmZvdlNlw0C4phg8lGKYFzoL+DPPL4/TrvkZ6h1QU/uHUiU
a0L41O9jI6HsnQ/dS7OzG7V+Gcgduv0gUvdc0wK+km2BtBtnR7nG4501hGd//xjZ
D4XN+WpBsr6PL7XawXyg0cHDEbBvq/yHqy3mTkBW9/d5EdAlWjVTuj6FhaMouZQr
fBIiEAlWl0iZsxa8VbVBFvZHJcAyS5rut1KINO7yXgdZ0Pa58nppJJ8P3DSJ8WkP
vQzvQ6GRuU/0FdKRS/gvvQak1kEa+2vHM3y911ivlppPAdqXu6CszqMi5H5GmI27
4JGq0MJ5h9xltz7+k3EpmriztRHnqoFyG9a4cI8NR5aTtHLc5GzXJBPQ7xKbvf2M
xY/qy9pEtCw6SbKO9I6+oEruVS1UOl9LAG7ATFItWGm0dHw7HXp0EpNhwmo2Si5n
Yc1OdBasCOxA7yRBxzvEtSNfeY0BiDniIAtuWpFVQ/sUY3ao+Aiz+9ATRYSXtBKb
HtXP9pMGM9Oa9L0SADXsQbopt7M8rkgLXD6DkLBq/LMenqp5vkMP8WBqBl45g1yG
8n8EBmohylFP+L0kSI7oHr7+zJu7EZnpUP2jsHR9+8coBTia1zfvrLSq2wZV8W/d
WAFvJzJKWbhrNxzLYLyh
=+Key
-----END PGP SIGNATURE-----
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 12:51 ` Koen Kooi
@ 2012-05-18 12:53 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 12:53 UTC (permalink / raw)
To: openembedded-devel; +Cc: meta-ti
Hello Koen,
>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>> affects both projects one way or the other.
>>
>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>> However, both compilers break the kernel we're using
>> (ti81xx-psp-linux-2.6.37).
>
> What happens when you disable the mailbox? AIUI you shouldn't need that on
> Ne/Ce.
How do I disable the mailbox? What do you mean by Ne/Ce?
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 12:53 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 12:53 UTC (permalink / raw)
To: openembedded-devel; +Cc: meta-ti
Hello Koen,
>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>> affects both projects one way or the other.
>>
>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>> However, both compilers break the kernel we're using
>> (ti81xx-psp-linux-2.6.37).
>
> What happens when you disable the mailbox? AIUI you shouldn't need that on
> Ne/Ce.
How do I disable the mailbox? What do you mean by Ne/Ce?
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 12:53 ` [oe] " Thilo Fromm
@ 2012-05-18 12:55 ` Koen Kooi
-1 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 12:55 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, openembedded-devel
Op 18 mei 2012, om 14:53 heeft Thilo Fromm het volgende geschreven:
> Hello Koen,
>
>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>> affects both projects one way or the other.
>>>
>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>> However, both compilers break the kernel we're using
>>> (ti81xx-psp-linux-2.6.37).
>>
>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>> Ne/Ce.
>
> How do I disable the mailbox?
In the .config
> What do you mean by Ne/Ce?
Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 12:55 ` Koen Kooi
0 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 12:55 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, openembedded-devel
Op 18 mei 2012, om 14:53 heeft Thilo Fromm het volgende geschreven:
> Hello Koen,
>
>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>> affects both projects one way or the other.
>>>
>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>> However, both compilers break the kernel we're using
>>> (ti81xx-psp-linux-2.6.37).
>>
>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>> Ne/Ce.
>
> How do I disable the mailbox?
In the .config
> What do you mean by Ne/Ce?
Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 12:55 ` [oe] " Koen Kooi
@ 2012-05-18 13:39 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 13:39 UTC (permalink / raw)
To: Koen Kooi; +Cc: meta-ti, openembedded-devel
Hello Koen,
>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>> affects both projects one way or the other.
>>>>
>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>> However, both compilers break the kernel we're using
>>>> (ti81xx-psp-linux-2.6.37).
>>>
>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>> Ne/Ce.
>>
>> How do I disable the mailbox?
>
> In the .config
Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
bridge. Disabling it would mean cutting off our DSP. No way.
>> What do you mean by Ne/Ce?
>
> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
C674x DSP. I think the only ones left without DSPs are AM-...
processors. So no, the DSP bridge (and therefore mailboxing) must
stay.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 13:39 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 13:39 UTC (permalink / raw)
To: Koen Kooi; +Cc: meta-ti, openembedded-devel
Hello Koen,
>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>> affects both projects one way or the other.
>>>>
>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>> However, both compilers break the kernel we're using
>>>> (ti81xx-psp-linux-2.6.37).
>>>
>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>> Ne/Ce.
>>
>> How do I disable the mailbox?
>
> In the .config
Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
bridge. Disabling it would mean cutting off our DSP. No way.
>> What do you mean by Ne/Ce?
>
> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
C674x DSP. I think the only ones left without DSPs are AM-...
processors. So no, the DSP bridge (and therefore mailboxing) must
stay.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 13:39 ` [oe] " Thilo Fromm
@ 2012-05-18 13:52 ` Koen Kooi
-1 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 13:52 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, openembedded-devel
Op 18 mei 2012, om 15:39 heeft Thilo Fromm het volgende geschreven:
> Hello Koen,
>
>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>>> affects both projects one way or the other.
>>>>>
>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>>> However, both compilers break the kernel we're using
>>>>> (ti81xx-psp-linux-2.6.37).
>>>>
>>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>>> Ne/Ce.
>>>
>>> How do I disable the mailbox?
>>
>> In the .config
>
> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> bridge. Disabling it would mean cutting off our DSP. No way.
Are you actually using dspbridge? Or are you using dsplink or syslink?
>
>>> What do you mean by Ne/Ce?
>>
>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
>
> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
> C674x DSP.
So a centaurus family SoC.
> I think the only ones left without DSPs are AM-...
> processors. So no, the DSP bridge (and therefore mailboxing) must
> stay.
See what I said above, I doubt you're using dspbridge.
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 13:52 ` Koen Kooi
0 siblings, 0 replies; 35+ messages in thread
From: Koen Kooi @ 2012-05-18 13:52 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, openembedded-devel
Op 18 mei 2012, om 15:39 heeft Thilo Fromm het volgende geschreven:
> Hello Koen,
>
>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>>> affects both projects one way or the other.
>>>>>
>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>>> However, both compilers break the kernel we're using
>>>>> (ti81xx-psp-linux-2.6.37).
>>>>
>>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>>> Ne/Ce.
>>>
>>> How do I disable the mailbox?
>>
>> In the .config
>
> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> bridge. Disabling it would mean cutting off our DSP. No way.
Are you actually using dspbridge? Or are you using dsplink or syslink?
>
>>> What do you mean by Ne/Ce?
>>
>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
>
> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
> C674x DSP.
So a centaurus family SoC.
> I think the only ones left without DSPs are AM-...
> processors. So no, the DSP bridge (and therefore mailboxing) must
> stay.
See what I said above, I doubt you're using dspbridge.
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 13:52 ` [oe] " Koen Kooi
@ 2012-05-18 14:36 ` Monk, Roger
-1 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-05-18 14:36 UTC (permalink / raw)
To: Koen Kooi, Thilo Fromm
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On Fri, May 18, 2012 at 14:52:36, Koen Kooi wrote:
> Cc: meta-ti@yoctoproject.org;
> openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel
> with gcc > 4.5
>
>
> Op 18 mei 2012, om 15:39 heeft Thilo Fromm het volgende geschreven:
>
> > Hello Koen,
> >
> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >>>>> this affects both projects one way or the other.
> >>>>>
> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> >>>>> This means with oe-core + meta-oe you now can choose between
> >>>>> gcc-4.6
> and gcc-4.7.
> >>>>> However, both compilers break the kernel we're using
> >>>>> (ti81xx-psp-linux-2.6.37).
> >>>>
> >>>> What happens when you disable the mailbox? AIUI you shouldn't
> >>>> need that on Ne/Ce.
> >>>
> >>> How do I disable the mailbox?
> >>
> >> In the .config
> >
> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> > bridge. Disabling it would mean cutting off our DSP. No way.
>
> Are you actually using dspbridge? Or are you using dsplink or syslink?
>
> >
> >>> What do you mean by Ne/Ce?
> >>
> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> calling it nowadays.
> >
> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> > a C674x DSP.
>
> So a centaurus family SoC.
Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
>
> > I think the only ones left without DSPs are AM-...
> > processors. So no, the DSP bridge (and therefore mailboxing) must
> > stay.
>
> See what I said above, I doubt you're using dspbridge.
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
_______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 14:36 ` Monk, Roger
0 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-05-18 14:36 UTC (permalink / raw)
To: Koen Kooi, Thilo Fromm
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On Fri, May 18, 2012 at 14:52:36, Koen Kooi wrote:
> Cc: meta-ti@yoctoproject.org;
> openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel
> with gcc > 4.5
>
>
> Op 18 mei 2012, om 15:39 heeft Thilo Fromm het volgende geschreven:
>
> > Hello Koen,
> >
> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >>>>> this affects both projects one way or the other.
> >>>>>
> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> >>>>> This means with oe-core + meta-oe you now can choose between
> >>>>> gcc-4.6
> and gcc-4.7.
> >>>>> However, both compilers break the kernel we're using
> >>>>> (ti81xx-psp-linux-2.6.37).
> >>>>
> >>>> What happens when you disable the mailbox? AIUI you shouldn't
> >>>> need that on Ne/Ce.
> >>>
> >>> How do I disable the mailbox?
> >>
> >> In the .config
> >
> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> > bridge. Disabling it would mean cutting off our DSP. No way.
>
> Are you actually using dspbridge? Or are you using dsplink or syslink?
>
> >
> >>> What do you mean by Ne/Ce?
> >>
> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> calling it nowadays.
> >
> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> > a C674x DSP.
>
> So a centaurus family SoC.
Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
>
> > I think the only ones left without DSPs are AM-...
> > processors. So no, the DSP bridge (and therefore mailboxing) must
> > stay.
>
> See what I said above, I doubt you're using dspbridge.
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
_______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 14:36 ` [oe] " Monk, Roger
@ 2012-05-18 14:55 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 14:55 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org, Koen Kooi,
openembedded-devel@lists.openembedded.org
Hello Roger,
>> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>> >>>>> this affects both projects one way or the other.
>> >>>>>
>> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>> >>>>> This means with oe-core + meta-oe you now can choose between
>> >>>>> gcc-4.6 and gcc-4.7.
>> >>>>> However, both compilers break the kernel we're using
>> >>>>> (ti81xx-psp-linux-2.6.37).
>> >>>>
>> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>> > a C674x DSP.
>>
>> So a centaurus family SoC.
>
> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
What are you trying to do? printk-debugging? Via E-Mail? Are you
serious? I provided a simple procedure to reproduce the issue. Please
reproduce and fix the problem.
> Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
Please do that, go there and take a look.
We'll be using gcc-4.5 in the HidaV layer until TI fixes this mess.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 14:55 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 14:55 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
Hello Roger,
>> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>> >>>>> this affects both projects one way or the other.
>> >>>>>
>> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>> >>>>> This means with oe-core + meta-oe you now can choose between
>> >>>>> gcc-4.6 and gcc-4.7.
>> >>>>> However, both compilers break the kernel we're using
>> >>>>> (ti81xx-psp-linux-2.6.37).
>> >>>>
>> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>> > a C674x DSP.
>>
>> So a centaurus family SoC.
>
> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
What are you trying to do? printk-debugging? Via E-Mail? Are you
serious? I provided a simple procedure to reproduce the issue. Please
reproduce and fix the problem.
> Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
Please do that, go there and take a look.
We'll be using gcc-4.5 in the HidaV layer until TI fixes this mess.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 14:55 ` [oe] " Thilo Fromm
@ 2012-05-23 9:48 ` Steffen Sledz
-1 siblings, 0 replies; 35+ messages in thread
From: Steffen Sledz @ 2012-05-23 9:48 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
Hi Roger!
On 18.05.2012 16:55, Thilo Fromm wrote:
>>>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>>>>>>>> this affects both projects one way or the other.
>>>>>>>>
>>>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>>>>>>>> This means with oe-core + meta-oe you now can choose between
>>>>>>>> gcc-4.6 and gcc-4.7.
>>>>>>>> However, both compilers break the kernel we're using
>>>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>>>
>>>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>>>> a C674x DSP.
>>>
>>> So a centaurus family SoC.
>>
>> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>
> What are you trying to do? printk-debugging? Via E-Mail? Are you
> serious? I provided a simple procedure to reproduce the issue. Please
> reproduce and fix the problem.
Ping!
Could you reproduce the bug?
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-23 9:48 ` Steffen Sledz
0 siblings, 0 replies; 35+ messages in thread
From: Steffen Sledz @ 2012-05-23 9:48 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
Hi Roger!
On 18.05.2012 16:55, Thilo Fromm wrote:
>>>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>>>>>>>> this affects both projects one way or the other.
>>>>>>>>
>>>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>>>>>>>> This means with oe-core + meta-oe you now can choose between
>>>>>>>> gcc-4.6 and gcc-4.7.
>>>>>>>> However, both compilers break the kernel we're using
>>>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>>>
>>>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>>>> a C674x DSP.
>>>
>>> So a centaurus family SoC.
>>
>> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>
> What are you trying to do? printk-debugging? Via E-Mail? Are you
> serious? I provided a simple procedure to reproduce the issue. Please
> reproduce and fix the problem.
Ping!
Could you reproduce the bug?
Steffen
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-23 9:48 ` [oe] " Steffen Sledz
@ 2012-06-11 14:22 ` Steffen Sledz
-1 siblings, 0 replies; 35+ messages in thread
From: Steffen Sledz @ 2012-06-11 14:22 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On 23.05.2012 11:48, Steffen Sledz wrote:
> Hi Roger!
>
> On 18.05.2012 16:55, Thilo Fromm wrote:
>>>>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>>>>>>>>> this affects both projects one way or the other.
>>>>>>>>>
>>>>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>>>>>>>>> This means with oe-core + meta-oe you now can choose between
>>>>>>>>> gcc-4.6 and gcc-4.7.
>>>>>>>>> However, both compilers break the kernel we're using
>>>>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>>>>
>>>>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>>>>> a C674x DSP.
>>>>
>>>> So a centaurus family SoC.
>>>
>>> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>>
>> What are you trying to do? printk-debugging? Via E-Mail? Are you
>> serious? I provided a simple procedure to reproduce the issue. Please
>> reproduce and fix the problem.
>
> Ping!
>
> Could you reproduce the bug?
FYI
According to [1] we track the progress on this issue at [2].
[1] <https://lists.yoctoproject.org/pipermail/meta-ti/2012-June/001242.html>
[2] <https://github.com/DFE/HidaV/issues/5>
Steffen Sledz
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-06-11 14:22 ` Steffen Sledz
0 siblings, 0 replies; 35+ messages in thread
From: Steffen Sledz @ 2012-06-11 14:22 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On 23.05.2012 11:48, Steffen Sledz wrote:
> Hi Roger!
>
> On 18.05.2012 16:55, Thilo Fromm wrote:
>>>>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>>>>>>>>> this affects both projects one way or the other.
>>>>>>>>>
>>>>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>>>>>>>>> This means with oe-core + meta-oe you now can choose between
>>>>>>>>> gcc-4.6 and gcc-4.7.
>>>>>>>>> However, both compilers break the kernel we're using
>>>>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>>>>
>>>>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>>>>> a C674x DSP.
>>>>
>>>> So a centaurus family SoC.
>>>
>>> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>>
>> What are you trying to do? printk-debugging? Via E-Mail? Are you
>> serious? I provided a simple procedure to reproduce the issue. Please
>> reproduce and fix the problem.
>
> Ping!
>
> Could you reproduce the bug?
FYI
According to [1] we track the progress on this issue at [2].
[1] <https://lists.yoctoproject.org/pipermail/meta-ti/2012-June/001242.html>
[2] <https://github.com/DFE/HidaV/issues/5>
Steffen Sledz
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 14:36 ` [oe] " Monk, Roger
@ 2012-06-19 14:43 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-06-19 14:43 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org, Koen Kooi,
openembedded-devel@lists.openembedded.org
Hello Roger,
>> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>> >>>>> this affects both projects one way or the other.
>> >>>>>
>> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>> >>>>> This means with oe-core + meta-oe you now can choose between
>> >>>>> gcc-4.6 and gcc-4.7.
>> >>>>> However, both compilers break the kernel we're using
>> >>>>> (ti81xx-psp-linux-2.6.37).
>> >>>>
>> >>>> What happens when you disable the mailbox? AIUI you shouldn't
>> >>>> need that on Ne/Ce.
>> >>>
>> >>> How do I disable the mailbox?
>> >>
>> >> In the .config
>> >
>> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
>> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
>> > bridge. Disabling it would mean cutting off our DSP. No way.
>>
>> Are you actually using dspbridge? Or are you using dsplink or syslink?
>>
>> >>> What do you mean by Ne/Ce?
>> >>
>> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
>> calling it nowadays.
>> >
>> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>> > a C674x DSP.
>>
>> So a centaurus family SoC.
>
> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>
> Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
So did you put your printks in there and then run the code? Were you
able to reproduce the issue?
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-06-19 14:43 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-06-19 14:43 UTC (permalink / raw)
To: Monk, Roger
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
Hello Roger,
>> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
>> >>>>> this affects both projects one way or the other.
>> >>>>>
>> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
>> >>>>> This means with oe-core + meta-oe you now can choose between
>> >>>>> gcc-4.6 and gcc-4.7.
>> >>>>> However, both compilers break the kernel we're using
>> >>>>> (ti81xx-psp-linux-2.6.37).
>> >>>>
>> >>>> What happens when you disable the mailbox? AIUI you shouldn't
>> >>>> need that on Ne/Ce.
>> >>>
>> >>> How do I disable the mailbox?
>> >>
>> >> In the .config
>> >
>> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
>> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
>> > bridge. Disabling it would mean cutting off our DSP. No way.
>>
>> Are you actually using dspbridge? Or are you using dsplink or syslink?
>>
>> >>> What do you mean by Ne/Ce?
>> >>
>> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
>> calling it nowadays.
>> >
>> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
>> > a C674x DSP.
>>
>> So a centaurus family SoC.
>
> Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
>
> Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
So did you put your printks in there and then run the code? Were you
able to reproduce the issue?
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-06-19 14:43 ` [oe] " Thilo Fromm
@ 2012-06-19 22:27 ` Monk, Roger
-1 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-06-19 22:27 UTC (permalink / raw)
To: Thilo Fromm
Cc: meta-ti@yoctoproject.org, Koen Kooi,
openembedded-devel@lists.openembedded.org
Hello Thilo,
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
-----Original Message-----
> From: Thilo Fromm [mailto:fromm@dresearch-fe.de]
> Sent: 19 June 2012 15:43
> To: Monk, Roger
> Cc: Koen Kooi; meta-ti@yoctoproject.org; openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
>
> Hello Roger,
>
> >> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >> >>>>> this affects both projects one way or the other.
> >> >>>>>
> >> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> >> >>>>> This means with oe-core + meta-oe you now can choose between
> >> >>>>> gcc-4.6 and gcc-4.7.
> >> >>>>> However, both compilers break the kernel we're using
> >> >>>>> (ti81xx-psp-linux-2.6.37).
> >> >>>>
> >> >>>> What happens when you disable the mailbox? AIUI you shouldn't
> >> >>>> need that on Ne/Ce.
> >> >>>
> >> >>> How do I disable the mailbox?
> >> >>
> >> >> In the .config
> >> >
> >> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> >> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> >> > bridge. Disabling it would mean cutting off our DSP. No way.
> >>
> >> Are you actually using dspbridge? Or are you using dsplink or syslink?
> >>
> >> >>> What do you mean by Ne/Ce?
> >> >>
> >> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> >> calling it nowadays.
> >> >
> >> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> >> > a C674x DSP.
> >>
> >> So a centaurus family SoC.
> >
> > Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
> >
> > Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
>
> So did you put your printks in there and then run the code? Were you able to reproduce the issue?
I'm afraid this is not a platform that I am working with unfortunately, so I'm not able to help directly with this issue. My previous comments were in an attempt to try to help you (or others) to progress further with the debug of this issue.
> Regards,
> Thilo
> --
> Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
> Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
> Fax: +49 (30) 515 932 77 http://www.dresearch.de
> Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058
> Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-06-19 22:27 ` Monk, Roger
0 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-06-19 22:27 UTC (permalink / raw)
To: Thilo Fromm
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
Hello Thilo,
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
-----Original Message-----
> From: Thilo Fromm [mailto:fromm@dresearch-fe.de]
> Sent: 19 June 2012 15:43
> To: Monk, Roger
> Cc: Koen Kooi; meta-ti@yoctoproject.org; openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
>
> Hello Roger,
>
> >> >>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >> >>>>> this affects both projects one way or the other.
> >> >>>>>
> >> >>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> >> >>>>> This means with oe-core + meta-oe you now can choose between
> >> >>>>> gcc-4.6 and gcc-4.7.
> >> >>>>> However, both compilers break the kernel we're using
> >> >>>>> (ti81xx-psp-linux-2.6.37).
> >> >>>>
> >> >>>> What happens when you disable the mailbox? AIUI you shouldn't
> >> >>>> need that on Ne/Ce.
> >> >>>
> >> >>> How do I disable the mailbox?
> >> >>
> >> >> In the .config
> >> >
> >> > Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> >> > need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> >> > bridge. Disabling it would mean cutting off our DSP. No way.
> >>
> >> Are you actually using dspbridge? Or are you using dsplink or syslink?
> >>
> >> >>> What do you mean by Ne/Ce?
> >> >>
> >> >> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> >> calling it nowadays.
> >> >
> >> > We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> >> > a C674x DSP.
> >>
> >> So a centaurus family SoC.
> >
> > Can you put some printk's in omap_mbox_register (plat-omap/mailbox.c) to print the list objects, in particular the mbox->name?
> >
> > Would also be useful to see the same in omap_mbox_get() before the call to strcmp().
>
> So did you put your printks in there and then run the code? Were you able to reproduce the issue?
I'm afraid this is not a platform that I am working with unfortunately, so I'm not able to help directly with this issue. My previous comments were in an attempt to try to help you (or others) to progress further with the debug of this issue.
> Regards,
> Thilo
> --
> Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
> Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
> Fax: +49 (30) 515 932 77 http://www.dresearch.de
> Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr. DE273952058
> Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 13:52 ` [oe] " Koen Kooi
@ 2012-05-18 14:40 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 14:40 UTC (permalink / raw)
To: Koen Kooi; +Cc: meta-ti, openembedded-devel
Hello Koen,
>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>>>> affects both projects one way or the other.
>>>>>>
>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>>>> However, both compilers break the kernel we're using
>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>
>>>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>>>> Ne/Ce.
>>>>
>>>> How do I disable the mailbox?
>>>
>>> In the .config
>>
>> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
>> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
>> bridge. Disabling it would mean cutting off our DSP. No way.
>
> Are you actually using dspbridge? Or are you using dsplink or syslink?
No, I was wrong. OMAP_MBOX_FWK is forced to "Y" in our config and I
thought DSPBRIDGE forced this. But DSPBRIDGE isn't even active in our
configuration. I cannot turn OMAP_MBOX_FWK off, it's forced to Y, and
I'm currently trying to figure out which part of
ti81xx-psp-linux-2.6.37's wicked configuration is causing this.
>>>> What do you mean by Ne/Ce?
>>>
>>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
>>
>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
>> C674x DSP.
>
> So a centaurus family SoC.
Thanks for the clarification :) TI didn't approach us with any of the
terms you mentioned. It's just DaVinci for them when they're talking
with us.
>
>> I think the only ones left without DSPs are AM-...
>> processors. So no, the DSP bridge (and therefore mailboxing) must
>> stay.
>
> See what I said above, I doubt you're using dspbridge.
You may be right; I didn't dig into DSP communication so far. Also,
DSPBRIDGE depends on OMAP3, which we don't have (dm8148 is a
"OMAP2PLUS"). So I was wrong with DSPBRIDGE forcing OMAP_MBOX_FWK.
OMAP_MBOX_FWK is just active and I can't switch it off.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 14:40 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-18 14:40 UTC (permalink / raw)
To: Koen Kooi; +Cc: meta-ti, openembedded-devel
Hello Koen,
>>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think this
>>>>>> affects both projects one way or the other.
>>>>>>
>>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5. This means
>>>>>> with oe-core + meta-oe you now can choose between gcc-4.6 and gcc-4.7.
>>>>>> However, both compilers break the kernel we're using
>>>>>> (ti81xx-psp-linux-2.6.37).
>>>>>
>>>>> What happens when you disable the mailbox? AIUI you shouldn't need that on
>>>>> Ne/Ce.
>>>>
>>>> How do I disable the mailbox?
>>>
>>> In the .config
>>
>> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
>> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
>> bridge. Disabling it would mean cutting off our DSP. No way.
>
> Are you actually using dspbridge? Or are you using dsplink or syslink?
No, I was wrong. OMAP_MBOX_FWK is forced to "Y" in our config and I
thought DSPBRIDGE forced this. But DSPBRIDGE isn't even active in our
configuration. I cannot turn OMAP_MBOX_FWK off, it's forced to Y, and
I'm currently trying to figure out which part of
ti81xx-psp-linux-2.6.37's wicked configuration is causing this.
>>>> What do you mean by Ne/Ce?
>>>
>>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
>>
>> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
>> C674x DSP.
>
> So a centaurus family SoC.
Thanks for the clarification :) TI didn't approach us with any of the
terms you mentioned. It's just DaVinci for them when they're talking
with us.
>
>> I think the only ones left without DSPs are AM-...
>> processors. So no, the DSP bridge (and therefore mailboxing) must
>> stay.
>
> See what I said above, I doubt you're using dspbridge.
You may be right; I didn't dig into DSP communication so far. Also,
DSPBRIDGE depends on OMAP3, which we don't have (dm8148 is a
"OMAP2PLUS"). So I was wrong with DSPBRIDGE forcing OMAP_MBOX_FWK.
OMAP_MBOX_FWK is just active and I can't switch it off.
Regards,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 14:40 ` [oe] " Thilo Fromm
@ 2012-05-18 14:47 ` Monk, Roger
-1 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-05-18 14:47 UTC (permalink / raw)
To: Thilo Fromm, Koen Kooi
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On Fri, May 18, 2012 at 15:40:25, Thilo Fromm wrote:
> Cc: meta-ti@yoctoproject.org;
> openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel
> with gcc > 4.5
>
> Hello Koen,
>
> >>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >>>>>> this affects both projects one way or the other.
> >>>>>>
> >>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> This
> >>>>>> means with oe-core + meta-oe you now can choose between gcc-4.6
> and gcc-4.7.
> >>>>>> However, both compilers break the kernel we're using
> >>>>>> (ti81xx-psp-linux-2.6.37).
> >>>>>
> >>>>> What happens when you disable the mailbox? AIUI you shouldn't
> need
> >>>>> that on Ne/Ce.
> >>>>
> >>>> How do I disable the mailbox?
> >>>
> >>> In the .config
> >>
> >> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> >> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> >> bridge. Disabling it would mean cutting off our DSP. No way.
> >
> > Are you actually using dspbridge? Or are you using dsplink or
> syslink?
>
> No, I was wrong. OMAP_MBOX_FWK is forced to "Y" in our config and I
> thought DSPBRIDGE forced this. But DSPBRIDGE isn't even active in our
> configuration. I cannot turn OMAP_MBOX_FWK off, it's forced to Y, and
> I'm currently trying to figure out which part of ti81xx-psp-linux-
> 2.6.37's wicked configuration is causing this.
CONFIG_SYSLINK_NOTIFY turns this on. Syslink uses the same mbox infrastructure.
>
> >>>> What do you mean by Ne/Ce?
> >>>
> >>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> calling it nowadays.
> >>
> >> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> a
> >> C674x DSP.
> >
> > So a centaurus family SoC.
>
> Thanks for the clarification :) TI didn't approach us with any of the
> terms you mentioned. It's just DaVinci for them when they're talking
> with us.
>
> >
> >> I think the only ones left without DSPs are AM-...
> >> processors. So no, the DSP bridge (and therefore mailboxing) must
> >> stay.
> >
> > See what I said above, I doubt you're using dspbridge.
>
> You may be right; I didn't dig into DSP communication so far. Also,
> DSPBRIDGE depends on OMAP3, which we don't have (dm8148 is a
> "OMAP2PLUS"). So I was wrong with DSPBRIDGE forcing OMAP_MBOX_FWK.
> OMAP_MBOX_FWK is just active and I can't switch it off.
>
> Regards,
> Thilo
>
> --
> Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch
> Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
> Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
> Fax: +49 (30) 515 932 77 http://www.dresearch.de
> Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr.
> DE273952058
> Geschäftsführer: Dr. M. Weber, W. Mögle
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
_______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 14:47 ` Monk, Roger
0 siblings, 0 replies; 35+ messages in thread
From: Monk, Roger @ 2012-05-18 14:47 UTC (permalink / raw)
To: Thilo Fromm, Koen Kooi
Cc: meta-ti@yoctoproject.org,
openembedded-devel@lists.openembedded.org
On Fri, May 18, 2012 at 15:40:25, Thilo Fromm wrote:
> Cc: meta-ti@yoctoproject.org;
> openembedded-devel@lists.openembedded.org
> Subject: Re: [meta-ti] [oe] ti81xx-psp-linux-2.6.37: broken kernel
> with gcc > 4.5
>
> Hello Koen,
>
> >>>>>> sorry for the cross-post (openembedded-devel, meta-ti), I think
> >>>>>> this affects both projects one way or the other.
> >>>>>>
> >>>>>> Recently, meta-openembedded/toolchain-layer removed gcc-4.5.
> This
> >>>>>> means with oe-core + meta-oe you now can choose between gcc-4.6
> and gcc-4.7.
> >>>>>> However, both compilers break the kernel we're using
> >>>>>> (ti81xx-psp-linux-2.6.37).
> >>>>>
> >>>>> What happens when you disable the mailbox? AIUI you shouldn't
> need
> >>>>> that on Ne/Ce.
> >>>>
> >>>> How do I disable the mailbox?
> >>>
> >>> In the .config
> >>
> >> Wait wait wait, according to drivers/staging/tidspbridge/Kconfig we
> >> need OMAP_MBOX_FWK (i.e. "the mailbox") in order to use the DSP
> >> bridge. Disabling it would mean cutting off our DSP. No way.
> >
> > Are you actually using dspbridge? Or are you using dsplink or
> syslink?
>
> No, I was wrong. OMAP_MBOX_FWK is forced to "Y" in our config and I
> thought DSPBRIDGE forced this. But DSPBRIDGE isn't even active in our
> configuration. I cannot turn OMAP_MBOX_FWK off, it's forced to Y, and
> I'm currently trying to figure out which part of ti81xx-psp-linux-
> 2.6.37's wicked configuration is causing this.
CONFIG_SYSLINK_NOTIFY turns this on. Syslink uses the same mbox infrastructure.
>
> >>>> What do you mean by Ne/Ce?
> >>>
> >>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is
> calling it nowadays.
> >>
> >> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with
> a
> >> C674x DSP.
> >
> > So a centaurus family SoC.
>
> Thanks for the clarification :) TI didn't approach us with any of the
> terms you mentioned. It's just DaVinci for them when they're talking
> with us.
>
> >
> >> I think the only ones left without DSPs are AM-...
> >> processors. So no, the DSP bridge (and therefore mailboxing) must
> >> stay.
> >
> > See what I said above, I doubt you're using dspbridge.
>
> You may be right; I didn't dig into DSP communication so far. Also,
> DSPBRIDGE depends on OMAP3, which we don't have (dm8148 is a
> "OMAP2PLUS"). So I was wrong with DSPBRIDGE forcing OMAP_MBOX_FWK.
> OMAP_MBOX_FWK is just active and I can't switch it off.
>
> Regards,
> Thilo
>
> --
> Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect DResearch
> Fahrzeugelektronik GmbH Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
> Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
> Fax: +49 (30) 515 932 77 http://www.dresearch.de
> Amtsgericht: Berlin Charlottenburg, HRB 130120 B Ust.-IDNr.
> DE273952058
> Geschäftsführer: Dr. M. Weber, W. Mögle
>
Texas Instruments Limited, 800 Pavilion Drive, Northampton, NN4 7YL. Registered in England & Wales under company number 00574102
_______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 14:40 ` [oe] " Thilo Fromm
@ 2012-05-18 21:48 ` Denys Dmytriyenko
-1 siblings, 0 replies; 35+ messages in thread
From: Denys Dmytriyenko @ 2012-05-18 21:48 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, Koen Kooi, openembedded-devel
On Fri, May 18, 2012 at 04:40:25PM +0200, Thilo Fromm wrote:
>
> >>>> What do you mean by Ne/Ce?
> >>>
> >>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
> >>
> >> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
> >> C674x DSP.
> >
> > So a centaurus family SoC.
>
> Thanks for the clarification :) TI didn't approach us with any of the
> terms you mentioned. It's just DaVinci for them when they're talking
> with us.
Netra and Centaurus are internal codenames for the SoC families behind those
part numbers Koen mentioned above. Those codenames are not publicly advertised
and Koen is just showing off after being on the inside... :) :-P
--
Denys
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-18 21:48 ` Denys Dmytriyenko
0 siblings, 0 replies; 35+ messages in thread
From: Denys Dmytriyenko @ 2012-05-18 21:48 UTC (permalink / raw)
To: Thilo Fromm; +Cc: meta-ti, openembedded-devel
On Fri, May 18, 2012 at 04:40:25PM +0200, Thilo Fromm wrote:
>
> >>>> What do you mean by Ne/Ce?
> >>>
> >>> Netra/Centaurus, dm81xx, c6a81xx, am38xx, am39xx or whatever TI is calling it nowadays.
> >>
> >> We're on a "TI DaVinci DM8148", featuring a cortex-a8 combined with a
> >> C674x DSP.
> >
> > So a centaurus family SoC.
>
> Thanks for the clarification :) TI didn't approach us with any of the
> terms you mentioned. It's just DaVinci for them when they're talking
> with us.
Netra and Centaurus are internal codenames for the SoC families behind those
part numbers Koen mentioned above. Those codenames are not publicly advertised
and Koen is just showing off after being on the inside... :) :-P
--
Denys
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-18 21:48 ` [oe] " Denys Dmytriyenko
@ 2012-05-19 8:22 ` Eric Bénard
-1 siblings, 0 replies; 35+ messages in thread
From: Eric Bénard @ 2012-05-19 8:22 UTC (permalink / raw)
To: openembedded-devel; +Cc: meta-ti, Koen Kooi, Thilo Fromm
Hi Denys,
Le Fri, 18 May 2012 17:48:33 -0400,
Denys Dmytriyenko <denis@denix.org> a écrit :
> Netra and Centaurus are internal codenames for the SoC families behind those
> part numbers Koen mentioned above. Those codenames are not publicly advertised
> and Koen is just showing off after being on the inside... :) :-P
>
these names were already dislosed on TI's website, for example :
http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
and are even in your slides where I first saw them ;-)
https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
Eric
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-19 8:22 ` Eric Bénard
0 siblings, 0 replies; 35+ messages in thread
From: Eric Bénard @ 2012-05-19 8:22 UTC (permalink / raw)
To: openembedded-devel; +Cc: meta-ti
Hi Denys,
Le Fri, 18 May 2012 17:48:33 -0400,
Denys Dmytriyenko <denis@denix.org> a écrit :
> Netra and Centaurus are internal codenames for the SoC families behind those
> part numbers Koen mentioned above. Those codenames are not publicly advertised
> and Koen is just showing off after being on the inside... :) :-P
>
these names were already dislosed on TI's website, for example :
http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
and are even in your slides where I first saw them ;-)
https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
Eric
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-19 8:22 ` [oe] " Eric Bénard
@ 2012-05-21 8:00 ` Thilo Fromm
-1 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-21 8:00 UTC (permalink / raw)
To: Eric Bénard; +Cc: meta-ti, Koen Kooi, openembedded-devel
Hello Eric,
>> Netra and Centaurus are internal codenames for the SoC families behind those
>> part numbers Koen mentioned above. Those codenames are not publicly advertised
>> and Koen is just showing off after being on the inside... :) :-P
>>
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
>
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
I guess Denys just wanted to show off a bit there by dropping code
names not publicly advertised, with him being on the inside, you know
>;)
Regars,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-21 8:00 ` Thilo Fromm
0 siblings, 0 replies; 35+ messages in thread
From: Thilo Fromm @ 2012-05-21 8:00 UTC (permalink / raw)
To: Eric Bénard; +Cc: meta-ti, openembedded-devel
Hello Eric,
>> Netra and Centaurus are internal codenames for the SoC families behind those
>> part numbers Koen mentioned above. Those codenames are not publicly advertised
>> and Koen is just showing off after being on the inside... :) :-P
>>
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
>
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
I guess Denys just wanted to show off a bit there by dropping code
names not publicly advertised, with him being on the inside, you know
>;)
Regars,
Thilo
--
Dipl.-Ing (FH) Thilo Fromm, MSc., Embedded Systems Architect
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, D-10319 Berlin, Germany
Tel: +49 (30) 515 932 228 mailto:fromm@dresearch-fe.de
Fax: +49 (30) 515 932 77 http://www.dresearch.de
Amtsgericht: Berlin Charlottenburg, HRB 130120 B
Ust.-IDNr. DE273952058
Geschäftsführer: Dr. M. Weber, W. Mögle
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [meta-ti] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
2012-05-19 8:22 ` [oe] " Eric Bénard
@ 2012-05-21 14:55 ` Denys Dmytriyenko
-1 siblings, 0 replies; 35+ messages in thread
From: Denys Dmytriyenko @ 2012-05-21 14:55 UTC (permalink / raw)
To: Eric B?nard; +Cc: meta-ti, Koen Kooi, openembedded-devel, Thilo Fromm
On Sat, May 19, 2012 at 10:22:15AM +0200, Eric B?nard wrote:
> Hi Denys,
>
> Le Fri, 18 May 2012 17:48:33 -0400,
> Denys Dmytriyenko <denis@denix.org> a ?crit :
> > Netra and Centaurus are internal codenames for the SoC families behind those
> > part numbers Koen mentioned above. Those codenames are not publicly advertised
> > and Koen is just showing off after being on the inside... :) :-P
> >
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
>
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
Good catch, but I didn't say they were secret :) I only said they were not
advertised or marketed as official platform names. You can always find those
references deep inside the code in several places...
So, it's understandable that customers may not know them, but it's fine to use
those references among the developers.
--
Denys
^ permalink raw reply [flat|nested] 35+ messages in thread
* Re: [oe] ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5
@ 2012-05-21 14:55 ` Denys Dmytriyenko
0 siblings, 0 replies; 35+ messages in thread
From: Denys Dmytriyenko @ 2012-05-21 14:55 UTC (permalink / raw)
To: Eric B?nard; +Cc: meta-ti, openembedded-devel
On Sat, May 19, 2012 at 10:22:15AM +0200, Eric B?nard wrote:
> Hi Denys,
>
> Le Fri, 18 May 2012 17:48:33 -0400,
> Denys Dmytriyenko <denis@denix.org> a ?crit :
> > Netra and Centaurus are internal codenames for the SoC families behind those
> > part numbers Koen mentioned above. Those codenames are not publicly advertised
> > and Koen is just showing off after being on the inside... :) :-P
> >
> these names were already dislosed on TI's website, for example :
> http://focus.ti.com/asia/download/1105-techday-abstracts-tw.pdf
> http://processors.wiki.ti.com/index.php/DM814x_AM387x_PSP_Flashing_Tools_Guide
>
> and are even in your slides where I first saw them ;-)
> https://wiki.yoctoproject.org/wiki/images/b/b3/Meta-ti.pdf
Good catch, but I didn't say they were secret :) I only said they were not
advertised or marketed as official platform names. You can always find those
references deep inside the code in several places...
So, it's understandable that customers may not know them, but it's fine to use
those references among the developers.
--
Denys
^ permalink raw reply [flat|nested] 35+ messages in thread
end of thread, other threads:[~2012-06-19 22:40 UTC | newest]
Thread overview: 35+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-18 12:33 ti81xx-psp-linux-2.6.37: broken kernel with gcc > 4.5 Thilo Fromm
2012-05-18 12:51 ` Koen Kooi
2012-05-18 12:51 ` Koen Kooi
2012-05-18 12:53 ` Thilo Fromm
2012-05-18 12:53 ` [oe] " Thilo Fromm
2012-05-18 12:55 ` [meta-ti] " Koen Kooi
2012-05-18 12:55 ` [oe] " Koen Kooi
2012-05-18 13:39 ` [meta-ti] " Thilo Fromm
2012-05-18 13:39 ` [oe] " Thilo Fromm
2012-05-18 13:52 ` [meta-ti] " Koen Kooi
2012-05-18 13:52 ` [oe] " Koen Kooi
2012-05-18 14:36 ` [meta-ti] " Monk, Roger
2012-05-18 14:36 ` [oe] " Monk, Roger
2012-05-18 14:55 ` [meta-ti] " Thilo Fromm
2012-05-18 14:55 ` [oe] " Thilo Fromm
2012-05-23 9:48 ` [meta-ti] " Steffen Sledz
2012-05-23 9:48 ` [oe] " Steffen Sledz
2012-06-11 14:22 ` [meta-ti] " Steffen Sledz
2012-06-11 14:22 ` [oe] " Steffen Sledz
2012-06-19 14:43 ` [meta-ti] " Thilo Fromm
2012-06-19 14:43 ` [oe] " Thilo Fromm
2012-06-19 22:27 ` [meta-ti] " Monk, Roger
2012-06-19 22:27 ` [oe] " Monk, Roger
2012-05-18 14:40 ` [meta-ti] " Thilo Fromm
2012-05-18 14:40 ` [oe] " Thilo Fromm
2012-05-18 14:47 ` [meta-ti] " Monk, Roger
2012-05-18 14:47 ` [oe] " Monk, Roger
2012-05-18 21:48 ` [meta-ti] " Denys Dmytriyenko
2012-05-18 21:48 ` [oe] " Denys Dmytriyenko
2012-05-19 8:22 ` [meta-ti] " Eric Bénard
2012-05-19 8:22 ` [oe] " Eric Bénard
2012-05-21 8:00 ` [meta-ti] " Thilo Fromm
2012-05-21 8:00 ` [oe] " Thilo Fromm
2012-05-21 14:55 ` [meta-ti] " Denys Dmytriyenko
2012-05-21 14:55 ` [oe] " Denys Dmytriyenko
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.