[meta-ti] [PATCH v2 1/3] debugss-module-drv: Add version 1.2.0

Jacob Stiffler j-stiffler at ti.com
Tue May 19 11:03:35 PDT 2015



On 5/19/2015 2:01 PM, Denys Dmytriyenko wrote:
> On Tue, May 19, 2015 at 01:56:29PM -0400, Jacob Stiffler wrote:
>>
>> On 5/19/2015 1:39 PM, Denys Dmytriyenko wrote:
>>> On Tue, May 19, 2015 at 07:26:59AM -0400, Jacob Stiffler wrote:
>>>> * The debugss-module-drv is require for the dsptop utility.
>>>>
>>>> Signed-off-by: Jacob Stiffler <j-stiffler at ti.com>
>>>> ---
>>>> * v2 changes:
>>>>    - Add support for k2hk-evm
>>>>    - Reorganize file based on oe-stylize.
>>>>
>>>>   recipes-bsp/dsptop/debugss-module-drv_git.bb |   22 ++++++++++++++++++++++
>>>>   recipes-bsp/dsptop/dsptop.inc                |    8 ++++++++
>>>>   2 files changed, 30 insertions(+)
>>>>   create mode 100644 recipes-bsp/dsptop/debugss-module-drv_git.bb
>>>>   create mode 100644 recipes-bsp/dsptop/dsptop.inc
>>>>
>>>> diff --git a/recipes-bsp/dsptop/debugss-module-drv_git.bb b/recipes-bsp/dsptop/debugss-module-drv_git.bb
>>>> new file mode 100644
>>>> index 0000000..c4edb8d
>>>> --- /dev/null
>>>> +++ b/recipes-bsp/dsptop/debugss-module-drv_git.bb
>>>> @@ -0,0 +1,22 @@
>>>> +DESCRIPTION = "Debug Sub-System (DebugSS) driver for Keystone and DRA7xx devices"
>>>> +LICENSE = "GPLv2"
>>>> +LIC_FILES_CHKSUM = "file://COPYING.txt;md5=9d4316fe434ba450dca4da25348ca5a3"
>>>> +
>>>> +# This package builds a kernel module, use kernel PR as base and append a local
>>>> +MACHINE_KERNEL_PR_append = "a+gitr${SRCPV}"
>>>> +PR = "${MACHINE_KERNEL_PR}"
>>>> +
>>>> +S = "${WORKDIR}/git/debugss_module/debugss-mod"
>>>> +
>>>> +inherit module
>>>> +
>>>> +PLATFORM = ""
>>>> +PLATFORM_dra7xx = "DRA7xx_PLATFORM"
>>>> +PLATFORM_k2hk-evm = "KEYSTONE_PLATFORM"
>>>> +
>>>> +EXTRA_OEMAKE = "'PLATFORM=${PLATFORM}'"
>>>> +
>>>> +COMPATIBLE_MACHINE = "dra7xx|k2hk-evm"
>>> So, is it really only limited to k2hk and not other Keystones?
>>>
>> I briefly looked through the source to get the platform options, and
>> I noticed that "K2H" is used in many of the #defines. Looking
>> closer, I see that KEYSTONE_PLATFORM appears to general to the
>> keystone family.
>>
>> In other recipes, DEVICE is used. This appears to be specific to
>> individual MACHINEs.
> Ok, can we use generic "keystone" SOC family when KEYSTONE_PLATFORM is used
> and a more stricter "k2hk-evm" machine when K2H DEVICE is used?
>

Sure. I'll make the changes in the v3.

>>>> +PACKAGE_ARCH = "${MACHINE_ARCH}"
>>>> +
>>>> +include dsptop.inc
>>>> diff --git a/recipes-bsp/dsptop/dsptop.inc b/recipes-bsp/dsptop/dsptop.inc
>>>> new file mode 100644
>>>> index 0000000..4b9e3fa
>>>> --- /dev/null
>>>> +++ b/recipes-bsp/dsptop/dsptop.inc
>>>> @@ -0,0 +1,8 @@
>>>> +# This corresponds to version 1.2.0
>>>> +SRCREV = "9893486936626e2d3de721f429a67fcac8a68151"
>>>> +PV = "1.2.0"
>>>> +INC_PR = "r0"
>>>> +
>>>> +SRC_URI = "git://git.ti.com/sdo-emu/dsptop.git;protocol=git;branch=${BRANCH}"
>>>> +
>>>> +BRANCH = "master"
>>>> -- 
>>>> 1.7.9.5
>>>>
>>>> -- 
>>>> _______________________________________________
>>>> meta-ti mailing list
>>>> meta-ti at yoctoproject.org
>>>> https://lists.yoctoproject.org/listinfo/meta-ti



More information about the meta-ti mailing list