* [PATCH 1/2] linux-ti-staging: Add OMAP5 support
@ 2013-03-19 15:10 Chase Maupin
2013-03-19 15:10 ` [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration Chase Maupin
0 siblings, 1 reply; 6+ messages in thread
From: Chase Maupin @ 2013-03-19 15:10 UTC (permalink / raw)
To: meta-ti
* Add the KERNEL_DEVICETREE definitions for omap5-evm
* Add the omap-a15 SOC_FAMILY to the list of COMPATIBLE_MACHINEs
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
---
recipes-kernel/linux/linux-ti-staging_git.bb | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/recipes-kernel/linux/linux-ti-staging_git.bb b/recipes-kernel/linux/linux-ti-staging_git.bb
index cfd4da0..3ff038d 100644
--- a/recipes-kernel/linux/linux-ti-staging_git.bb
+++ b/recipes-kernel/linux/linux-ti-staging_git.bb
@@ -32,8 +32,9 @@ DEPENDS_ti33x += "am33x-cm3"
# for the specific beaglebone machine.
KERNEL_DEVICETREE_ti33x = "arch/arm/boot/dts/am335x-evm.dts arch/arm/boot/dts/am335x-evmsk.dts arch/arm/boot/dts/am335x-bone.dts"
KERNEL_DEVICETREE_beaglebone = "arch/arm/boot/dts/am335x-bone.dts"
+KERNEL_DEVICETREE_omap5-evm = "arch/arm/boot/dts/omap5-evm.dts"
-COMPATIBLE_MACHINE = "ti33x"
+COMPATIBLE_MACHINE = "ti33x|omap-a15"
S = "${WORKDIR}/git"
--
1.7.0.4
^ permalink raw reply related [flat|nested] 6+ messages in thread
* [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
2013-03-19 15:10 [PATCH 1/2] linux-ti-staging: Add OMAP5 support Chase Maupin
@ 2013-03-19 15:10 ` Chase Maupin
2013-03-19 15:11 ` Maupin, Chase
2013-03-19 17:12 ` Denys Dmytriyenko
0 siblings, 2 replies; 6+ messages in thread
From: Chase Maupin @ 2013-03-19 15:10 UTC (permalink / raw)
To: meta-ti
* Add the machine configuration for the OMAP5 EVM device.
* Create the omap-a15.inc file to be shared with all Cortex-A15
derivative devices.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
---
conf/machine/include/omap-a15.inc | 18 ++++++++++++++++++
conf/machine/{am335x-evm.conf => omap5-evm.conf} | 20 ++++++++++++++------
2 files changed, 32 insertions(+), 6 deletions(-)
create mode 100644 conf/machine/include/omap-a15.inc
copy conf/machine/{am335x-evm.conf => omap5-evm.conf} (65%)
diff --git a/conf/machine/include/omap-a15.inc b/conf/machine/include/omap-a15.inc
new file mode 100644
index 0000000..3ea1a05
--- /dev/null
+++ b/conf/machine/include/omap-a15.inc
@@ -0,0 +1,18 @@
+SOC_FAMILY = "omap-a15"
+require conf/machine/include/soc-family.inc
+
+require conf/machine/include/tune-cortexa15.inc
+
+# Increase this everytime you change something in the kernel
+MACHINE_KERNEL_PR = "r0"
+
+PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"
+PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
+
+KERNEL_IMAGETYPE = "uImage"
+
+UBOOT_ARCH = "arm"
+UBOOT_ENTRYPOINT = "0x80008000"
+UBOOT_LOADADDRESS = "0x80008000"
+
+EXTRA_IMAGEDEPENDS += "virtual/bootloader"
diff --git a/conf/machine/am335x-evm.conf b/conf/machine/omap5-evm.conf
similarity index 65%
copy from conf/machine/am335x-evm.conf
copy to conf/machine/omap5-evm.conf
index 21e79a2..daa5f58 100644
--- a/conf/machine/am335x-evm.conf
+++ b/conf/machine/omap5-evm.conf
@@ -1,13 +1,15 @@
#@TYPE: Machine
-#@NAME: AM335x EVM
-#@DESCRIPTION: Machine configuration for the TI AM335x EVM
+#@NAME: OMAP5 EVM
+#@DESCRIPTION: Machine configuration for the TI OMAP5 uEVM
-require conf/machine/include/ti33x.inc
+PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
+XSERVER = "xserver-xorg \
+ xf86-input-evdev \
+ xf86-video-fbdev"
-# Use built-in LCD by default
-XSERVER += "xf86-input-tslib"
GUI_MACHINE_CLASS = "smallscreen"
-MACHINE_FEATURES += "touchscreen"
+
+require conf/machine/include/omap-a15.inc
IMAGE_FSTYPES += "ubi tar.gz"
@@ -33,3 +35,9 @@ MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 3836"
# UBI: sub-page size: 512
# UBI: VID header offset: 2048 (aligned 2048)
UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512 -O 2048"
+
+UBOOT_MACHINE = "omap5_evm_config"
+
+# Currently removing the sgx machine feature because there is no SGX package
+# available for omap5
+MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2 screen touchscreen"
--
1.7.0.4
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
2013-03-19 15:10 ` [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration Chase Maupin
@ 2013-03-19 15:11 ` Maupin, Chase
2013-03-19 17:12 ` Denys Dmytriyenko
1 sibling, 0 replies; 6+ messages in thread
From: Maupin, Chase @ 2013-03-19 15:11 UTC (permalink / raw)
To: Maupin, Chase, meta-ti@yoctoproject.org
> -----Original Message-----
> From: Maupin, Chase
> Sent: Tuesday, March 19, 2013 10:11 AM
> To: meta-ti@yoctoproject.org
> Cc: Maupin, Chase
> Subject: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
>
> * Add the machine configuration for the OMAP5 EVM device.
> * Create the omap-a15.inc file to be shared with all Cortex-A15
> derivative devices.
>
> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
> ---
> conf/machine/include/omap-a15.inc | 18
> ++++++++++++++++++
> conf/machine/{am335x-evm.conf => omap5-evm.conf} | 20
> ++++++++++++++------
> 2 files changed, 32 insertions(+), 6 deletions(-)
> create mode 100644 conf/machine/include/omap-a15.inc
> copy conf/machine/{am335x-evm.conf => omap5-evm.conf} (65%)
>
> diff --git a/conf/machine/include/omap-a15.inc
> b/conf/machine/include/omap-a15.inc
> new file mode 100644
> index 0000000..3ea1a05
> --- /dev/null
> +++ b/conf/machine/include/omap-a15.inc
> @@ -0,0 +1,18 @@
> +SOC_FAMILY = "omap-a15"
> +require conf/machine/include/soc-family.inc
> +
> +require conf/machine/include/tune-cortexa15.inc
> +
> +# Increase this everytime you change something in the kernel
> +MACHINE_KERNEL_PR = "r0"
> +
> +PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"
> +PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
Denys,
This is with the assumption that your u-boot patchset goes in first.
> +
> +KERNEL_IMAGETYPE = "uImage"
> +
> +UBOOT_ARCH = "arm"
> +UBOOT_ENTRYPOINT = "0x80008000"
> +UBOOT_LOADADDRESS = "0x80008000"
> +
> +EXTRA_IMAGEDEPENDS += "virtual/bootloader"
> diff --git a/conf/machine/am335x-evm.conf b/conf/machine/omap5-
> evm.conf
> similarity index 65%
> copy from conf/machine/am335x-evm.conf
> copy to conf/machine/omap5-evm.conf
> index 21e79a2..daa5f58 100644
> --- a/conf/machine/am335x-evm.conf
> +++ b/conf/machine/omap5-evm.conf
> @@ -1,13 +1,15 @@
> #@TYPE: Machine
> -#@NAME: AM335x EVM
> -#@DESCRIPTION: Machine configuration for the TI AM335x EVM
> +#@NAME: OMAP5 EVM
> +#@DESCRIPTION: Machine configuration for the TI OMAP5 uEVM
>
> -require conf/machine/include/ti33x.inc
> +PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
> +XSERVER = "xserver-xorg \
> + xf86-input-evdev \
> + xf86-video-fbdev"
>
> -# Use built-in LCD by default
> -XSERVER += "xf86-input-tslib"
> GUI_MACHINE_CLASS = "smallscreen"
> -MACHINE_FEATURES += "touchscreen"
> +
> +require conf/machine/include/omap-a15.inc
>
> IMAGE_FSTYPES += "ubi tar.gz"
>
> @@ -33,3 +35,9 @@ MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 3836"
> # UBI: sub-page size: 512
> # UBI: VID header offset: 2048 (aligned 2048)
> UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512 -O 2048"
> +
> +UBOOT_MACHINE = "omap5_evm_config"
> +
> +# Currently removing the sgx machine feature because there is no
> SGX package
> +# available for omap5
> +MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2
> screen touchscreen"
> --
> 1.7.0.4
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
2013-03-19 15:10 ` [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration Chase Maupin
2013-03-19 15:11 ` Maupin, Chase
@ 2013-03-19 17:12 ` Denys Dmytriyenko
2013-03-19 19:29 ` Maupin, Chase
1 sibling, 1 reply; 6+ messages in thread
From: Denys Dmytriyenko @ 2013-03-19 17:12 UTC (permalink / raw)
To: Chase Maupin; +Cc: meta-ti
On Tue, Mar 19, 2013 at 10:10:41AM -0500, Chase Maupin wrote:
> * Add the machine configuration for the OMAP5 EVM device.
Overall looks good.
> * Create the omap-a15.inc file to be shared with all Cortex-A15
> derivative devices.
Is the omap-a15 a preferred name? I didn't see it used internally anywhere.
It's not like I object specifically to this name, but was wondering if there
was something else other people are more familiar with? Another option would
be just simple "omap5", but I guess you are planning for few of those new
derivative platforms that don't really have omap5 in the name... :)
Moreover, the comment above implies omap-a15 SoC file will be used for all
Cortex-A15 devices, which is not exactly correct, as Keystone has nothing to
do with omap5 and shouldn't share that SoC file.
--
Denys
> Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
> ---
> conf/machine/include/omap-a15.inc | 18 ++++++++++++++++++
> conf/machine/{am335x-evm.conf => omap5-evm.conf} | 20 ++++++++++++++------
> 2 files changed, 32 insertions(+), 6 deletions(-)
> create mode 100644 conf/machine/include/omap-a15.inc
> copy conf/machine/{am335x-evm.conf => omap5-evm.conf} (65%)
>
> diff --git a/conf/machine/include/omap-a15.inc b/conf/machine/include/omap-a15.inc
> new file mode 100644
> index 0000000..3ea1a05
> --- /dev/null
> +++ b/conf/machine/include/omap-a15.inc
> @@ -0,0 +1,18 @@
> +SOC_FAMILY = "omap-a15"
> +require conf/machine/include/soc-family.inc
> +
> +require conf/machine/include/tune-cortexa15.inc
> +
> +# Increase this everytime you change something in the kernel
> +MACHINE_KERNEL_PR = "r0"
> +
> +PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"
> +PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
> +
> +KERNEL_IMAGETYPE = "uImage"
> +
> +UBOOT_ARCH = "arm"
> +UBOOT_ENTRYPOINT = "0x80008000"
> +UBOOT_LOADADDRESS = "0x80008000"
> +
> +EXTRA_IMAGEDEPENDS += "virtual/bootloader"
> diff --git a/conf/machine/am335x-evm.conf b/conf/machine/omap5-evm.conf
> similarity index 65%
> copy from conf/machine/am335x-evm.conf
> copy to conf/machine/omap5-evm.conf
> index 21e79a2..daa5f58 100644
> --- a/conf/machine/am335x-evm.conf
> +++ b/conf/machine/omap5-evm.conf
> @@ -1,13 +1,15 @@
> #@TYPE: Machine
> -#@NAME: AM335x EVM
> -#@DESCRIPTION: Machine configuration for the TI AM335x EVM
> +#@NAME: OMAP5 EVM
> +#@DESCRIPTION: Machine configuration for the TI OMAP5 uEVM
>
> -require conf/machine/include/ti33x.inc
> +PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
> +XSERVER = "xserver-xorg \
> + xf86-input-evdev \
> + xf86-video-fbdev"
>
> -# Use built-in LCD by default
> -XSERVER += "xf86-input-tslib"
> GUI_MACHINE_CLASS = "smallscreen"
> -MACHINE_FEATURES += "touchscreen"
> +
> +require conf/machine/include/omap-a15.inc
>
> IMAGE_FSTYPES += "ubi tar.gz"
>
> @@ -33,3 +35,9 @@ MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 3836"
> # UBI: sub-page size: 512
> # UBI: VID header offset: 2048 (aligned 2048)
> UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512 -O 2048"
> +
> +UBOOT_MACHINE = "omap5_evm_config"
> +
> +# Currently removing the sgx machine feature because there is no SGX package
> +# available for omap5
> +MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2 screen touchscreen"
> --
> 1.7.0.4
>
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
2013-03-19 17:12 ` Denys Dmytriyenko
@ 2013-03-19 19:29 ` Maupin, Chase
2013-03-19 19:51 ` Denys Dmytriyenko
0 siblings, 1 reply; 6+ messages in thread
From: Maupin, Chase @ 2013-03-19 19:29 UTC (permalink / raw)
To: Dmytriyenko, Denys; +Cc: meta-ti@yoctoproject.org
> -----Original Message-----
> From: Dmytriyenko, Denys
> Sent: Tuesday, March 19, 2013 12:13 PM
> To: Maupin, Chase
> Cc: meta-ti@yoctoproject.org
> Subject: Re: [meta-ti] [PATCH 2/2] omap5-evm: Add OMAP5 EVM
> configuration
>
> On Tue, Mar 19, 2013 at 10:10:41AM -0500, Chase Maupin wrote:
> > * Add the machine configuration for the OMAP5 EVM device.
>
> Overall looks good.
>
> > * Create the omap-a15.inc file to be shared with all Cortex-A15
> > derivative devices.
>
> Is the omap-a15 a preferred name? I didn't see it used internally
> anywhere.
> It's not like I object specifically to this name, but was
> wondering if there
> was something else other people are more familiar with? Another
> option would
> be just simple "omap5", but I guess you are planning for few of
> those new
> derivative platforms that don't really have omap5 in the name...
> :)
>
> Moreover, the comment above implies omap-a15 SoC file will be
> used for all
> Cortex-A15 devices, which is not exactly correct, as Keystone has
> nothing to
> do with omap5 and shouldn't share that SoC file.
Good point. I'll change the comment. I was thinking of this because of the DRA7xx. I'm open to other SOC_FAMILY names though.
>
> --
> Denys
>
>
> > Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
> > ---
> > conf/machine/include/omap-a15.inc | 18
> ++++++++++++++++++
> > conf/machine/{am335x-evm.conf => omap5-evm.conf} | 20
> ++++++++++++++------
> > 2 files changed, 32 insertions(+), 6 deletions(-)
> > create mode 100644 conf/machine/include/omap-a15.inc
> > copy conf/machine/{am335x-evm.conf => omap5-evm.conf} (65%)
> >
> > diff --git a/conf/machine/include/omap-a15.inc
> b/conf/machine/include/omap-a15.inc
> > new file mode 100644
> > index 0000000..3ea1a05
> > --- /dev/null
> > +++ b/conf/machine/include/omap-a15.inc
> > @@ -0,0 +1,18 @@
> > +SOC_FAMILY = "omap-a15"
> > +require conf/machine/include/soc-family.inc
> > +
> > +require conf/machine/include/tune-cortexa15.inc
> > +
> > +# Increase this everytime you change something in the kernel
> > +MACHINE_KERNEL_PR = "r0"
> > +
> > +PREFERRED_PROVIDER_virtual/kernel = "linux-ti-staging"
> > +PREFERRED_PROVIDER_virtual/bootloader = "u-boot-ti-staging"
> > +
> > +KERNEL_IMAGETYPE = "uImage"
> > +
> > +UBOOT_ARCH = "arm"
> > +UBOOT_ENTRYPOINT = "0x80008000"
> > +UBOOT_LOADADDRESS = "0x80008000"
> > +
> > +EXTRA_IMAGEDEPENDS += "virtual/bootloader"
> > diff --git a/conf/machine/am335x-evm.conf b/conf/machine/omap5-
> evm.conf
> > similarity index 65%
> > copy from conf/machine/am335x-evm.conf
> > copy to conf/machine/omap5-evm.conf
> > index 21e79a2..daa5f58 100644
> > --- a/conf/machine/am335x-evm.conf
> > +++ b/conf/machine/omap5-evm.conf
> > @@ -1,13 +1,15 @@
> > #@TYPE: Machine
> > -#@NAME: AM335x EVM
> > -#@DESCRIPTION: Machine configuration for the TI AM335x EVM
> > +#@NAME: OMAP5 EVM
> > +#@DESCRIPTION: Machine configuration for the TI OMAP5 uEVM
> >
> > -require conf/machine/include/ti33x.inc
> > +PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg"
> > +XSERVER = "xserver-xorg \
> > + xf86-input-evdev \
> > + xf86-video-fbdev"
> >
> > -# Use built-in LCD by default
> > -XSERVER += "xf86-input-tslib"
> > GUI_MACHINE_CLASS = "smallscreen"
> > -MACHINE_FEATURES += "touchscreen"
> > +
> > +require conf/machine/include/omap-a15.inc
> >
> > IMAGE_FSTYPES += "ubi tar.gz"
> >
> > @@ -33,3 +35,9 @@ MKUBIFS_ARGS = "-F -m 2048 -e 126976 -c 3836"
> > # UBI: sub-page size: 512
> > # UBI: VID header offset: 2048 (aligned 2048)
> > UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512 -O 2048"
> > +
> > +UBOOT_MACHINE = "omap5_evm_config"
> > +
> > +# Currently removing the sgx machine feature because there is
> no SGX package
> > +# available for omap5
> > +MACHINE_FEATURES = "kernel26 apm usbgadget usbhost vfat ext2
> screen touchscreen"
> > --
> > 1.7.0.4
> >
> > _______________________________________________
> > meta-ti mailing list
> > meta-ti@yoctoproject.org
> > https://lists.yoctoproject.org/listinfo/meta-ti
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration
2013-03-19 19:29 ` Maupin, Chase
@ 2013-03-19 19:51 ` Denys Dmytriyenko
0 siblings, 0 replies; 6+ messages in thread
From: Denys Dmytriyenko @ 2013-03-19 19:51 UTC (permalink / raw)
To: Maupin, Chase; +Cc: meta-ti@yoctoproject.org
On Tue, Mar 19, 2013 at 03:29:55PM -0400, Maupin, Chase wrote:
> > -----Original Message-----
> > From: Dmytriyenko, Denys
> > Sent: Tuesday, March 19, 2013 12:13 PM
> > To: Maupin, Chase
> > Cc: meta-ti@yoctoproject.org
> > Subject: Re: [meta-ti] [PATCH 2/2] omap5-evm: Add OMAP5 EVM
> > configuration
> >
> > On Tue, Mar 19, 2013 at 10:10:41AM -0500, Chase Maupin wrote:
> > > * Add the machine configuration for the OMAP5 EVM device.
> >
> > Overall looks good.
> >
> > > * Create the omap-a15.inc file to be shared with all Cortex-A15
> > > derivative devices.
> >
> > Is the omap-a15 a preferred name? I didn't see it used internally
> > anywhere.
> > It's not like I object specifically to this name, but was
> > wondering if there
> > was something else other people are more familiar with? Another
> > option would
> > be just simple "omap5", but I guess you are planning for few of
> > those new
> > derivative platforms that don't really have omap5 in the name...
> > :)
> >
> > Moreover, the comment above implies omap-a15 SoC file will be
> > used for all
> > Cortex-A15 devices, which is not exactly correct, as Keystone has
> > nothing to
> > do with omap5 and shouldn't share that SoC file.
>
> Good point. I'll change the comment. I was thinking of this because of the
> DRA7xx. I'm open to other SOC_FAMILY names though.
The more I think about it, the more omap-a15 feels appropriate - basically
highlighting and grouping OMAP-drived Cortex-A15 SoCs. Just make sure the
comment makes it clear, as there are other non-OMAP Cortex-A15 SoCs from TI.
--
Denys
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-03-19 19:51 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-03-19 15:10 [PATCH 1/2] linux-ti-staging: Add OMAP5 support Chase Maupin
2013-03-19 15:10 ` [PATCH 2/2] omap5-evm: Add OMAP5 EVM configuration Chase Maupin
2013-03-19 15:11 ` Maupin, Chase
2013-03-19 17:12 ` Denys Dmytriyenko
2013-03-19 19:29 ` Maupin, Chase
2013-03-19 19:51 ` 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.