meta/pandaboard: add pandaboard bsp
cover meta/pandaboard: add pandaboard bsp
From: Jingdong Lu <[email protected]>
Add pandaboard bsp
Jingdong Lu (1):
pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346 ++++++++++++++++++++ .../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.scc
PATCH 1/1 pandaboard: add pandaboard bsp
From: Jingdong Lu <[email protected]>
add pandaboard bsp configuration.
--- .../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346 ++++++++++++++++++++ .../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.scc
meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg new file +30 -0
@@ -0,0 +1,30 @@ +# +# Miscellaneous filesystems +# +CONFIG_NFS_DEF_FILE_IO_SIZE=1024 + +# +# Multiple Device Support +# +# CONFIG_MD is not set + +# Kernel Features +# +CONFIG_NO_HZ=y + +# +# CPUIdle +# +CONFIG_CPU_IDLE=y +CONFIG_CPU_IDLE_GOV_LADDER=y +CONFIG_CPU_IDLE_GOV_MENU=y + +# +# Kernel hacking +# +CONFIG_DEBUG_FS=y + +# +# Power management options +# +CONFIG_PM_DEBUG=y
meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc new file +7 -0
@@ -0,0 +1,7 @@ +define KMACHINE pandaboard +define KTYPE standard +define KARCH arm + +scc_leaf ktypes/standard pandaboard + +include pandaboard.scc
meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg new file +346 -0
346 lines not on this page · raw message
meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.scc new file +5 -0
@@ -0,0 +1,5 @@ +kconf hardware pandaboard.cfg +kconf non-hardware pandaboard-non_hardware.cfg + +include features/usb-net/usb-net.scc +include cfg/usb-mass-storage.scc
Signature · 1 line
1.7.0.4
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 3 lines · On 08/04/2011 10:58 PM, [email protected] wrote:
From: Jingdong Lu <[email protected]>
Add pandaboard bsp
why not use meta-ti ?
Quoted 16 lines
Jingdong Lu (1): pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346++++++++++++++++++++
.../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files
changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.scc
Quoted 2 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
=PeJ+
-----END PGP SIGNATURE-----
Quoted 9 lines · Khem Raj
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · On 08/04/2011 10:58 PM, [email protected] wrote:
From: Jingdong Lu<[email protected]>
Add pandaboard bsp
why not use meta-ti ?
I'm hoping to not repeat all the discussions that we've had around the beagle board here. Anything that applies to that applies here.
This is a reference BSP done by the Wind River folks on top of the linux-yocto kernel. It is not intended to be a replacement for any existing pandaboard efforts, but is intended to be used as an example of an integrated board.
Cheers,
Bruce
Quoted 34 lines
Quoted 17 lines
Jingdong Lu (1): pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346++++++++++++++++++++
.../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files
changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.sccQuoted 2 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
=PeJ+
-----END PGP SIGNATURE-----
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 11 lines · Bruce Ashfield
Quoted 9 lines · Khem Raj
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · On 08/04/2011 10:58 PM, [email protected] wrote:
From: Jingdong Lu<[email protected]>
Add pandaboard bsp
why not use meta-ti ?
Quoted 8 lines
I'm hoping to not repeat all the discussions that we've had around the beagle board here. Anything that applies to that applies here.
This is a reference BSP done by the Wind River folks on top of the linux-yocto kernel. It is not intended to be a replacement for any existing pandaboard efforts, but is intended to be used as an example of an integrated board.
Would you mind re-summarizing the discussion? I know there has been a lot of back and forth, and it seems like a summary would be helpful for people who stopped following the discussion.
It is very confusing for many of us to see duplicate and or competing BSP's.
Philip
Quoted 45 lines
Cheers,
Bruce
Quoted 26 lines
Quoted 17 lines
Jingdong Lu (1): pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346
++++++++++++++++++++
.../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.sccQuoted 2 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)Quoted 8 lines
iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
=PeJ+
-----END PGP SIGNATURE-----
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 16 lines · Philip Balister
Quoted 15 lines · Bruce Ashfield
Quoted 9 lines · Khem Raj
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · On 08/04/2011 10:58 PM, [email protected] wrote:
From: Jingdong Lu<[email protected]>
Add pandaboard bsp
why not use meta-ti ?
I'm hoping to not repeat all the discussions that we've had around the beagle board here. Anything that applies to that applies here.
Quoted 8 lines
Quoted 4 lines
This is a reference BSP done by the Wind River folks on top of the linux-yocto kernel. It is not intended to be a replacement for any existing pandaboard efforts, but is intended to be used as an example of an integrated board.
Would you mind re-summarizing the discussion? I know there has been a lot of back and forth, and it seems like a summary would be helpful for people who stopped following the discussion.
Darren's the right person to give a proper summary, since he was driving our beagleboard work. But he's out on Jury duty at the moment, so we'll have to wait. I can attempt a quick summary here.
The goal of a BSP like this as part of meta-yocto and linux-yocto are this for any BSP:
Goals:
1) <vendor/semi> needs meta-<vendor/semi> to maintain its role as the definitive source for <vendor/semi> BSPs and drive
fragmentation down.
2) The Yocto Project meta-yocto layer has a goal to provide stand-alone BSPs that demonstrates the multi-architecture features of the Yocto Project.
To to this, we have the challenges:
A) Using meta-<vendor/semi> with the Yocto Project
B) Aligning on kernel versions
C) Kernel policy definition and ownership
D) Not detract from upstream-first efforts .. and more.
So the meta-<foo> issues will be solved going forward with layer tooling, the kernel version alignment will never be solved completely but can be addressed via working with the right upstream and sources with the right process.
So to get that kernel alignment, tooling, common feature set and have a set of BSPs that can share tests, results, support, etc, there is a need to do yocto integrations of identified BSPs. We've (largely) agreed to live with some repeated effort in the short term and recognize that what you see here is not intended to replace a community or vendor effort, but should be considered as a stepping stone and proof of concept. If the latest and greatest, bleeding edge is what people want, then the other meta-* layers are the way to go.
I think that's enough for now, I tried to do the conversations justice and keep this short, so my apologies to anyone reading this if I missed something.
Cheers,
Bruce
Quoted 51 lines
It is very confusing for many of us to see duplicate and or competing BSP's.
Philip
Quoted 45 lines
Cheers,
Bruce
Quoted 26 lines
Quoted 17 lines
Jingdong Lu (1): pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346
++++++++++++++++++++
.../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.sccQuoted 2 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)Quoted 8 lines
iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
=PeJ+
-----END PGP SIGNATURE-----
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
Quoted 55 lines · Bruce Ashfield
Quoted 16 lines · Philip Balister
Quoted 15 lines · Bruce Ashfield
Quoted 9 lines · Khem Raj
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1Quoted 3 lines · On 08/04/2011 10:58 PM, [email protected] wrote:
From: Jingdong Lu<[email protected]>
Add pandaboard bsp
why not use meta-ti ?
I'm hoping to not repeat all the discussions that we've had around the beagle board here. Anything that applies to that applies here.
Quoted 8 lines
Quoted 4 lines
This is a reference BSP done by the Wind River folks on top of the linux-yocto kernel. It is not intended to be a replacement for any existing pandaboard efforts, but is intended to be used as an example of an integrated board.
Would you mind re-summarizing the discussion? I know there has been a lot of back and forth, and it seems like a summary would be helpful for people who stopped following the discussion.
Darren's the right person to give a proper summary, since he was driving our beagleboard work. But he's out on Jury duty at the moment, so we'll have to wait. I can attempt a quick summary here.
The goal of a BSP like this as part of meta-yocto and linux-yocto are this for any BSP:
Goals:
1) <vendor/semi> needs meta-<vendor/semi> to maintain its role as the definitive source for <vendor/semi> BSPs and drive fragmentation down.
2) The Yocto Project meta-yocto layer has a goal to provide stand-alone BSPs that demonstrates the multi-architecture features of the Yocto Project.To to this, we have the challenges:
A) Using meta-<vendor/semi> with the Yocto Project
B) Aligning on kernel versions
C) Kernel policy definition and ownership
D) Not detract from upstream-first efforts .. and more.So the meta-<foo> issues will be solved going forward with layer tooling, the kernel version alignment will never be solved completely but can be addressed via working with the right upstream and sources with the right process.
Quoted 9 lines
So to get that kernel alignment, tooling, common feature set and have a set of BSPs that can share tests, results, support, etc, there is a need to do yocto integrations of identified BSPs. We've (largely) agreed to live with some repeated effort in the short term and recognize that what you see here is not intended to replace a community or vendor effort, but should be considered as a stepping stone and proof of concept. If the latest and greatest, bleeding edge is what people want, then the other meta-* layers are the way to go.
I was thinking about this point over the weekend, and I realized that it may not have been clear that I'm talking largely about the kernel here. Not all the associated userspace/config, etc that we'd consider as part of a complete solution. Obviously any kernel tree can support multiple boards, and what we have here is an example against the 2.6.37 yocto kernel tree and kernel feature set.
Cheers,
Bruce
Quoted 67 lines
I think that's enough for now, I tried to do the conversations justice and keep this short, so my apologies to anyone reading this if I missed something.
Cheers,
Bruce
Quoted 51 lines
It is very confusing for many of us to see duplicate and or competing BSP's.
Philip
Quoted 45 lines
Cheers,
Bruce
Quoted 26 lines
Quoted 17 lines
Jingdong Lu (1): pandaboard: add pandaboard bsp
.../bsp/pandaboard/pandaboard-non_hardware.cfg | 30 ++ .../bsp/pandaboard/pandaboard-standard.scc | 7 + .../cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg | 346
++++++++++++++++++++
.../cfg/kernel-cache/bsp/pandaboard/pandaboard.scc | 5 + 4 files changed, 388 insertions(+), 0 deletions(-) create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-non_hardware.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.cfg create mode 100644 meta/cfg/kernel-cache/bsp/pandaboard/pandaboard.sccQuoted 2 lines
_______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
- --
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)Quoted 8 lines
iEYEARECAAYFAk48KZcACgkQuwUzVZGdMxSjEwCdHLqsMwcYEhAblghgJio7tJPK Sm8An2Xps8CntGIGV0bFxTJw/dIAL6pV
=PeJ+
-----END PGP SIGNATURE-----
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto