Cape Manager

Cape Manager

[Life Life]

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

Hello,

I'm trying build yocto based linux, My hardware is beaglebone black I
successfull build system image. But I can't see capemanager. Beacuse my lcd
is not work.

Thanks

[-- Attachment #2: Type: text/html, Size: 245 bytes --]

Re: Cape Manager

[Robert Yang]

On 06/30/2014 12:24 AM, Life Life wrote:
> Hello,
>
> I'm trying build yocto based linux, My hardware is beaglebone black I
> successfull build system image. But I can't see capemanager. Beacuse my lcd is
> not work.

Hello,

The cape manager is in meta-ti layer:

http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/

Seems that we'd better add it to meta-yoco-bsp ?

Add Saul in the loop.

>
> Thanks
>
>

Re: Cape Manager

[Life Life]

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

Please tell me how to add this layer to Yocto ? I'm using Hob interface


2014-06-30 6:46 GMT+03:00 Robert Yang <liezhi.yang@windriver.com>:

>
> On 06/30/2014 12:24 AM, Life Life wrote:
>
>> Hello,
>>
>> I'm trying build yocto based linux, My hardware is beaglebone black I
>> successfull build system image. But I can't see capemanager. Beacuse my
>> lcd is
>> not work.
>>
>
> Hello,
>
> The cape manager is in meta-ti layer:
>
> http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
>
> Seems that we'd better add it to meta-yoco-bsp ?
>
> Add Saul in the loop.
>
>
>> Thanks
>>
>>
>>

[-- Attachment #2: Type: text/html, Size: 1390 bytes --]

Re: Cape Manager

[Anders Darander]

* Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:


> On 06/30/2014 12:24 AM, Life Life wrote:
> > Hello,

> > I'm trying build yocto based linux, My hardware is beaglebone black I
> > successfull build system image. But I can't see capemanager. Beacuse my lcd is
> > not work.

> Hello,

> The cape manager is in meta-ti layer:

> http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/

> Seems that we'd better add it to meta-yoco-bsp ?

Unless something has changed since I last looked at this, I don't think
so. 

If I remember correctly, capemgr basically consists of a number of
patches not in the mainline kernel (and also not in TI's staging
kernel). I haven't checked it, by I doubt that we have them in the
linux-yocto kernel. (Especially as the last time I checked it, you had
to revert to a 3.8 (if I rember correctly, it might have been an even
earlier kernel) kernel to get full capemgr support.

If this has changed, then it'd be interesting to know!

Cheers,
Anders

> Add Saul in the loop.


-- 
Anders Darander
ChargeStorm AB / eStorm AB

Re: Cape Manager

[Life Life]

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

Hello,

I add ti-meta but capemgr is not work

This my boot log

Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.14.0-yocto-standard
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4985304 Bytes = 4.8 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f8a207

Starting kernel ...

Booting Linux on physical CPU 0x0
Initializing cgroup subsys cpuset
Initializing cgroup subsys cpu
Initializing cgroup subsys cpuacct
Linux version 3.14.0-yocto-standard (panda@pandabook) (gcc version 4.8.2
(GCC) ) #1 PREEMPT Fri Jun 27 15:16:56 EEST 2014
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine model: TI AM335x BeagleBone
cma: CMA: reserved 16 MiB at 9e800000
Memory policy: Data cache writeback
CPU: All CPU(s) started in SVC mode.
AM335X ES2.1 (sgx neon )
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129792
Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 ro
rootfstype=ext4 rootwait
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
allocated 1048576 bytes of page_cgroup
please try 'cgroup_disable=memory' option if you don't want memory cgroups
Memory: 489448K/523264K available (7491K kernel code, 520K rwdata, 2444K
rodata, 488K init, 757K bss, 33816K reserved, 0K highmem)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    vmalloc : 0xe0800000 - 0xff000000   ( 488 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
    modules : 0xbf000000 - 0xbfe00000   (  14 MB)
      .text : 0xc0008000 - 0xc09bc044   (9937 kB)
      .init : 0xc09bd000 - 0xc0a37034   ( 489 kB)
      .data : 0xc0a38000 - 0xc0aba0d4   ( 521 kB)
       .bss : 0xc0aba0d4 - 0xc0b77678   ( 758 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:16 nr_irqs:16 16
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
OMAP clockevent source: timer2 at 24000000 Hz
sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956969942ns
OMAP clocksource: timer1 at 24000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 548.86 BogoMIPS (lpj=2744320)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
Initializing cgroup subsys debug
Initializing cgroup subsys memory
Initializing cgroup subsys devices
Initializing cgroup subsys freezer
Initializing cgroup subsys net_cls
Initializing cgroup subsys blkio
CPU: Testing write buffer coherency: ok
ftrace: allocating 25107 entries in 74 pages
Setting up static identity map for 0x806c4000 - 0x806c4058
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_hwmod: tptc0 using broken dt data from edma
omap_hwmod: tptc1 using broken dt data from edma
omap_hwmod: tptc2 using broken dt data from edma
omap_hwmod: debugss: _wait_target_disable failed
xor: measuring software checksum speed
   arm4regs  :   685.200 MB/sec
   8regs     :   504.800 MB/sec
   32regs    :   658.800 MB/sec
xor: using function: arm4regs (685.200 MB/sec)
pinctrl core: initialized pinctrl subsystem
regulator-dummy: no parameters
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor ladder
cpuidle: using governor menu
platform 49000000.edma: alias fck already exists
platform 49000000.edma: alias fck already exists
platform 49000000.edma: alias fck already exists
OMAP GPIO hardware version 0.1
hw-breakpoint: debug architecture 0x4 unsupported.
bio: create slab <bio-0> at 0
raid6: int32x1     89 MB/s
raid6: int32x2    107 MB/s
raid6: int32x4     90 MB/s
raid6: int32x8     92 MB/s
raid6: using algorithm int32x2 (107 MB/s)
raid6: using intx1 recovery algorithm
edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
vmmcsd_fixed: 3300 mV
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
omap_i2c 44e0b000.i2c: could not find pctldev for node
/pinmux@44e10800/pinmux_i2c0_pins,
deferring probe
platform 44e0b000.i2c: Driver omap_i2c requests probe deferral
cfg80211: Calling CRDA to update world regulatory domain
Switched to clocksource timer1
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
TCP: reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available
futex hash table entries: 256 (order: -1, 3072 bytes)
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
msgmni has been set to 987
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
omap_uart 44e09000.serial: no wakeirq for uart0
44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000)
is a OMAP UART0
console [ttyO0] enabled
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
mtdoops: mtd device (mtddev=name/number) must be supplied
usbcore: registered new interface driver kaweth
pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver asix
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver smsc75xx
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver MOSCHIP usb-ethernet driver
usbcore: registered new interface driver int51x1
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-omap: OMAP-EHCI Host Controller driver
usbcore: registered new interface driver usb-storage
mousedev: PS/2 mouse device common for all mice
omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
i2c /dev entries driver
omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
48060000.mmc supply vmmc_aux not found, using dummy regulator
481d8000.mmc supply vmmc_aux not found, using dummy regulator
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
oprofile: using arm/armv7
u32 classifier
    Actions configured
TCP: cubic registered
NET: Registered protocol family 10
sit: IPv6 over IPv4 tunneling driver
NET: Registered protocol family 17
mmc0: host does not support reading read-only switch. assuming write-enable.
Key type dns_resolver registered
ThumbEE CPU extension supported.
mmc0: new high speed SDHC card at address 0001
bio: create slab <bio-1> at 1
mmcblk0: mmc0:0001 ASTC 7.38 GiB
 mmcblk0: p1 p2
Btrfs loaded
regulator-dummy: disabling
slave hdmi.6: could not get i2c
platform hdmi.6: Driver slave requests probe deferral
platform 4830e000.lcdc: Driver tilcdc requests probe deferral
DCDC1: at 1500 mV
vdd_mpu: 925 <--> 1325 mV at 1100 mV
vdd_core: 925 <--> 1150 mV at 1100 mV
LDO1: at 1800 mV
LDO2: at 3300 mV
LDO3: 1800 mV
LDO4: at 3300 mV
tps65217 0-0024: TPS65217 ID 0xe version 1.2
omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
mmc1: BKOPS_EN bit is not set
mmc1: new high speed MMC card at address 0001
mmcblk1: mmc1:0001 MMC02G 1.78 GiB
mmcblk1boot0: mmc1:0001 MMC02G partition 1 1.00 MiB
mmcblk1boot1: mmc1:0001 MMC02G partition 2 1.00 MiB
 mmcblk1: p1 p2
 mmcblk1boot1: unknown partition table
 mmcblk1boot0: unknown partition table
tilcdc 4830e000.lcdc: found TDA19988
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] No driver support for vblank timestamp query.
tilcdc 4830e000.lcdc: No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
Console: switching to colour frame buffer device 128x48
tilcdc 4830e000.lcdc: fb0:  frame buffer device
tilcdc 4830e000.lcdc: registered panic notifier
[drm] Initialized tilcdc 1.0.0 20121205 on minor 0
console [netcon0] enabled
netconsole: network logging started
davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
davinci_mdio 4a101000.mdio: detected phy mask fffffffe
libphy: 4a101000.mdio: probed
davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC
LAN8710/LAN8720
Detected MACID = 1c:ba:8c:f1:ec:e4
omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC
(946684800)
EXT4-fs (mmcblk0p2): mounted filesystem without journal. Opts: (null)
VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
devtmpfs: mounted
Freeing unused kernel memory: 488K (c09bd000 - c0a37000)
INIT: version 2.88 booting
Starting udev
udevd[82]: starting version 182
EXT4-fs (mmcblk0p2): warning: mounting unchecked fs, running e2fsck is
recommended
EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
Starting Bootlog daemon: bootlogd.
random: dd urandom read with 128 bits of entropy available
random: nonblocking pool is initialized
Mon Jun 30 07:45:00 UTC 2014
INIT: Entering runlevel: 5
Configuring network interfaces... net eth0: initializing cpsw version 1.12
(0)
net eth0: phy found : id is : 0x7c0f1
libphy: PHY 4a101000.mdio:01 not found
net eth0: phy 4a101000.mdio:01 not found on slave 1
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.22.1) started
Sending discover...
libphy: 4a101000.mdio:00 - Link is Up - 100/Full
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Sending discover...
Sending select for 192.168.50.1
Lease of 192.168.50.18 obtained, lease time 691200
/etc/udhcpc.d/50default: Adding DNS 192.168.50.1
/etc/udhcpc.d/50default: Adding DNS 192.168.50.1
done.
Starting OpenBSD Secure Shell server: sshd
done.
Starting syslogd/klogd: done
Stopping Bootlog daemon: bootlogd.

Poky (Yocto Project Reference Distro) 1.6.1 beaglebone /dev/ttyO0

I run this command

root@beaglebone:~# cape-stop.sh
hexdump: /sys/bus/i2c/devices/3-005*/eeprom: No such file or directory
unknown cape:




2014-06-30 11:15 GMT+03:00 Anders Darander <anders@chargestorm.se>:

> * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
>
>
> > On 06/30/2014 12:24 AM, Life Life wrote:
> > > Hello,
>
> > > I'm trying build yocto based linux, My hardware is beaglebone black I
> > > successfull build system image. But I can't see capemanager. Beacuse
> my lcd is
> > > not work.
>
> > Hello,
>
> > The cape manager is in meta-ti layer:
>
> > http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
>
> > Seems that we'd better add it to meta-yoco-bsp ?
>
> Unless something has changed since I last looked at this, I don't think
> so.
>
> If I remember correctly, capemgr basically consists of a number of
> patches not in the mainline kernel (and also not in TI's staging
> kernel). I haven't checked it, by I doubt that we have them in the
> linux-yocto kernel. (Especially as the last time I checked it, you had
> to revert to a 3.8 (if I rember correctly, it might have been an even
> earlier kernel) kernel to get full capemgr support.
>
> If this has changed, then it'd be interesting to know!
>
> Cheers,
> Anders
>
> > Add Saul in the loop.
>
>
> --
> Anders Darander
> ChargeStorm AB / eStorm AB
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 14793 bytes --]

Re: Cape Manager

[Anders Darander]

* Life Life <sadlife1990@gmail.com> [140630 10:37]:

> Hello,

> I add ti-meta but capemgr is not work

> Linux version 3.14.0-yocto-standard (panda@pandabook) (gcc version 4.8.2 (GCC)

I took a _really_ quick look at ti-linux-kernel (as well as
linux-yocto), neither one seems to include the capemgr-patches.

Cheers,
Anders


-- 
Anders Darander
ChargeStorm AB / eStorm AB

Re: Cape Manager

[Life Life]

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

Hello Again,

How to make ti-linux-kernel build hob ? or Angstrom distro ?

Thanks.


2014-06-30 11:49 GMT+03:00 Anders Darander <anders@chargestorm.se>:

> * Life Life <sadlife1990@gmail.com> [140630 10:37]:
>
> > Hello,
>
> > I add ti-meta but capemgr is not work
>
> > Linux version 3.14.0-yocto-standard (panda@pandabook) (gcc version
> 4.8.2 (GCC)
>
> I took a _really_ quick look at ti-linux-kernel (as well as
> linux-yocto), neither one seems to include the capemgr-patches.
>
> Cheers,
> Anders
>
>
> --
> Anders Darander
> ChargeStorm AB / eStorm AB
>

[-- Attachment #2: Type: text/html, Size: 1104 bytes --]

Re: Cape Manager

[Diego Sueiro]

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

On Mon, Jun 30, 2014 at 5:15 AM, Anders Darander <anders@chargestorm.se>
wrote:

> * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
>
>
> > On 06/30/2014 12:24 AM, Life Life wrote:
> > > Hello,
>
> > > I'm trying build yocto based linux, My hardware is beaglebone black I
> > > successfull build system image. But I can't see capemanager. Beacuse
> my lcd is
> > > not work.
>
> > Hello,
>
> > The cape manager is in meta-ti layer:
>
> > http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
>
> > Seems that we'd better add it to meta-yoco-bsp ?
>
> Unless something has changed since I last looked at this, I don't think
> so.
>
> If I remember correctly, capemgr basically consists of a number of
> patches not in the mainline kernel (and also not in TI's staging
> kernel). I haven't checked it, by I doubt that we have them in the
> linux-yocto kernel. (Especially as the last time I checked it, you had
> to revert to a 3.8 (if I rember correctly, it might have been an even
> earlier kernel) kernel to get full capemgr support.
>
> If this has changed, then it'd be interesting to know!
>
> Cheers,
> Anders
>

To get cape manager support you have to use meta-beagleboard layer (
linux-mainline_3.8.bb
<https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>
)



Regards,

--
*dS
Diego Sueiro

Administrador do Embarcados
www.embarcados.com.br
<http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>

/*long live rock 'n roll*/

[-- Attachment #2: Type: text/html, Size: 2964 bytes --]

Re: Cape Manager

[Life Life]

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

Hello,

How to use this layer, please explain

Thanks


2014-06-30 16:40 GMT+03:00 Diego Sueiro <diego.sueiro@gmail.com>:

>
> On Mon, Jun 30, 2014 at 5:15 AM, Anders Darander <anders@chargestorm.se>
> wrote:
>
>> * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
>>
>>
>> > On 06/30/2014 12:24 AM, Life Life wrote:
>> > > Hello,
>>
>> > > I'm trying build yocto based linux, My hardware is beaglebone black I
>> > > successfull build system image. But I can't see capemanager. Beacuse
>> my lcd is
>> > > not work.
>>
>> > Hello,
>>
>> > The cape manager is in meta-ti layer:
>>
>> > http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
>>
>> > Seems that we'd better add it to meta-yoco-bsp ?
>>
>> Unless something has changed since I last looked at this, I don't think
>> so.
>>
>> If I remember correctly, capemgr basically consists of a number of
>> patches not in the mainline kernel (and also not in TI's staging
>> kernel). I haven't checked it, by I doubt that we have them in the
>> linux-yocto kernel. (Especially as the last time I checked it, you had
>> to revert to a 3.8 (if I rember correctly, it might have been an even
>> earlier kernel) kernel to get full capemgr support.
>>
>> If this has changed, then it'd be interesting to know!
>>
>> Cheers,
>> Anders
>>
>
> To get cape manager support you have to use meta-beagleboard layer (
> linux-mainline_3.8.bb
> <https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>
> )
>
>
>
> Regards,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Embarcados
> www.embarcados.com.br
> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>
> /*long live rock 'n roll*/
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>

[-- Attachment #2: Type: text/html, Size: 3707 bytes --]

Re: Cape Manager

[Saul Wold]

On 06/30/2014 10:27 AM, Life Life wrote:
> Hello,
>
> How to use this layer, please explain
>

Have you referred to the Yocto Project Documentation?

https://www.yoctoproject.org/documentation/current

There is lots of information about adding layers and additional packages 
from those layers.

Look for information about bblayers file and make sure you also ensure 
you include the package in your image using

IMAGE_INSTALL_append = " beaglebone-capes"

The leading space in the line above is important

Sau!



> Thanks
>
>
> 2014-06-30 16:40 GMT+03:00 Diego Sueiro <diego.sueiro@gmail.com>:
>
>>
>> On Mon, Jun 30, 2014 at 5:15 AM, Anders Darander <anders@chargestorm.se>
>> wrote:
>>
>>> * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
>>>
>>>
>>>> On 06/30/2014 12:24 AM, Life Life wrote:
>>>>> Hello,
>>>
>>>>> I'm trying build yocto based linux, My hardware is beaglebone black I
>>>>> successfull build system image. But I can't see capemanager. Beacuse
>>> my lcd is
>>>>> not work.
>>>
>>>> Hello,
>>>
>>>> The cape manager is in meta-ti layer:
>>>
>>>> http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
>>>
>>>> Seems that we'd better add it to meta-yoco-bsp ?
>>>
>>> Unless something has changed since I last looked at this, I don't think
>>> so.
>>>
>>> If I remember correctly, capemgr basically consists of a number of
>>> patches not in the mainline kernel (and also not in TI's staging
>>> kernel). I haven't checked it, by I doubt that we have them in the
>>> linux-yocto kernel. (Especially as the last time I checked it, you had
>>> to revert to a 3.8 (if I rember correctly, it might have been an even
>>> earlier kernel) kernel to get full capemgr support.
>>>
>>> If this has changed, then it'd be interesting to know!
>>>
>>> Cheers,
>>> Anders
>>>
>>
>> To get cape manager support you have to use meta-beagleboard layer (
>> linux-mainline_3.8.bb
>> <https://github.com/beagleboard/meta-beagleboard/blob/master/common-bsp/recipes-kernel/linux/linux-mainline_3.8.bb>
>> )
>>
>>
>>
>> Regards,
>>
>> --
>> *dS
>> Diego Sueiro
>>
>> Administrador do Embarcados
>> www.embarcados.com.br
>> <http://www.embarcados.com.br/?utm_source=assinatura_diego&utm_medium=e-mail&utm_campaign=Assinatura%20Email%20Diego>
>>
>> /*long live rock 'n roll*/
>>
>> --
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
>
>
>

Re: Cape Manager

[Denys Dmytriyenko]

On Mon, Jun 30, 2014 at 10:15:07AM +0200, Anders Darander wrote:
> * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
> 
> 
> > On 06/30/2014 12:24 AM, Life Life wrote:
> > > Hello,
> 
> > > I'm trying build yocto based linux, My hardware is beaglebone black I
> > > successfull build system image. But I can't see capemanager. Beacuse my lcd is
> > > not work.
> 
> > Hello,
> 
> > The cape manager is in meta-ti layer:
> 
> > http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
> 
> > Seems that we'd better add it to meta-yoco-bsp ?
> 
> Unless something has changed since I last looked at this, I don't think
> so. 
> 
> If I remember correctly, capemgr basically consists of a number of
> patches not in the mainline kernel (and also not in TI's staging
> kernel). I haven't checked it, by I doubt that we have them in the
> linux-yocto kernel. (Especially as the last time I checked it, you had
> to revert to a 3.8 (if I rember correctly, it might have been an even
> earlier kernel) kernel to get full capemgr support.
> 
> If this has changed, then it'd be interesting to know!

That is correct - capemgr was a patchset against 3.8. It is not yet available 
in mainline. It was developed and being adopted for the mainline by Pantelis 
Antoniou and the community, but since it's rather a complicated subsystem, it 
went through numerous revisions and changes, still not merged upstream though.

-- 
Denys

Re: Cape Manager

[Life Life]

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

is it possible  lcd cape support without capemgr ?


2014-07-01 23:01 GMT+03:00 Denys Dmytriyenko <denis@denix.org>:

> On Mon, Jun 30, 2014 at 10:15:07AM +0200, Anders Darander wrote:
> > * Robert Yang <liezhi.yang@windriver.com> [140630 05:47]:
> >
> >
> > > On 06/30/2014 12:24 AM, Life Life wrote:
> > > > Hello,
> >
> > > > I'm trying build yocto based linux, My hardware is beaglebone black I
> > > > successfull build system image. But I can't see capemanager. Beacuse
> my lcd is
> > > > not work.
> >
> > > Hello,
> >
> > > The cape manager is in meta-ti layer:
> >
> > > http://layers.openembedded.org/layerindex/branch/master/layer/meta-ti/
> >
> > > Seems that we'd better add it to meta-yoco-bsp ?
> >
> > Unless something has changed since I last looked at this, I don't think
> > so.
> >
> > If I remember correctly, capemgr basically consists of a number of
> > patches not in the mainline kernel (and also not in TI's staging
> > kernel). I haven't checked it, by I doubt that we have them in the
> > linux-yocto kernel. (Especially as the last time I checked it, you had
> > to revert to a 3.8 (if I rember correctly, it might have been an even
> > earlier kernel) kernel to get full capemgr support.
> >
> > If this has changed, then it'd be interesting to know!
>
> That is correct - capemgr was a patchset against 3.8. It is not yet
> available
> in mainline. It was developed and being adopted for the mainline by
> Pantelis
> Antoniou and the community, but since it's rather a complicated subsystem,
> it
> went through numerous revisions and changes, still not merged upstream
> though.
>
> --
> Denys
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>

[-- Attachment #2: Type: text/html, Size: 2840 bytes --]