Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
On Wed, 2013-10-23 at 18:30 +0200, Björn Krombholz wrote:
On 10/20/2013 09:04 PM, Koen Kooi wrote:
Then I noticed that the 'genericarmv7a' machine in meta-linaro set
the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
that variable, but that's a different bug. It turns out that using
that tune we can have a single feed again for all armv7a machines.
Hi,
just for clarification, I'm not sure where to set it if not in the
MACHINE config without modifying meta-angstrom.
I've seen you added MACHINE specific DEFAULTTUNEs based on the currently
supported boards.
Basically the result should be (IMHO):
if MACHINE is a armv7a based and DISTRO is angstrom, then
DEFAULTTUNE = armv7athf-neon
Would it be possible to add those definitions based on SOC_FAMILY:
DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?
I hope so, see below.
As of now, when I add a new MACHINE=machfoo based on ti33x.inc from
meta-ti, I end up with a DEFAULTTUNE=armv7a-neon instead of the new one,
as the board is not known in meta-angstrom.
I added
DEFAULTTUNE_machfoo = ${DEFAULTTUNE_genericarmv7a}
to the machfoo.conf which is discouraged, if I understand you correctly.
Maybe I'm just missing the obvious safe way?
There is no obvious safe way :( You are running into the same problems
Khem and I ran into with the oe-core way of doing tune files.
This is a big problem and needs to get fixed somehow.
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] what file kernel configuration really uses?
On Wed, 2013-10-23 at 14:44 +0300, matti kaasinen wrote:
2013/10/23 Khem Raj raj.k...@gmail.com
Hi Ulf,
Yes, linux.inc seems doing the job as you told - this clears a lot. I had
been patching wrong file:${S}/defconfig instead of ${WORKDIR}/defconfig.
It seems that I'm not alone with this mistake. ${S}/defconfig seems to be
created by two patches:
0002-add-defconfig-file-to-use-as-.config.patch makes skeleton and
0073-defconfig-Update-bone-default-config.patch makes some modefications.
What I mean above is that beaglebone folks have made those patches for some
reason that is not quite clear tome now considering how ${S}/defconfig is
produced in linux.inc.
${S}/defconfig is neither used nor produced by OE.
${WORKDIR}/defconfig (important one) is most likely coming from
./linux/linux-mainline-3.8/beaglebone/defconfig as there is only one
difference that could have come from configuration process.
It seems that configuration fragments do not work in regular Angstrom - I
suppose they are just Yocto stuff.
yes.
Providing defconfig directly did not work - most likely it was written
over
by the patching the seems creating the ${WORKDIR}/defconfig
what do you mean ? defconfig is provided as any other file and then munged
over
in WORKDIR to make a .config
This is outdated information - wild quess - before I noticed how that
${S}/defconfig was really generated by those patches I explained above.
As I said above, ${S}/defconfig is not used in the build.
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Looking for an Angstrom and bitbake expert to consult / contract
On Fri, 2013-10-25 at 02:06 -0700, Khem Raj wrote: On Wed, Oct 23, 2013 at 3:42 PM, Edward Vidal vidal.devel...@gmail.com wrote: Hello Chris, I have been working with Yocto for beaglebone, beagleboard, pandaboard and now with the zedboard. I have tried angstrom but found yocto to be a better approach for me. I would like to emphasize that, Angstrom distribution is Yocto Project compatible and as the catchline for Yocto Project says, t's not an embedded Linux distribution – it creates a custom one for you Angstrom is one of those distributions. Now if you prefer Yocto Project's Reference Distribution and offer to customize it and create a distro for customer over something else thats fine however be clear about what you are trying to differentiate and even better why And on top of that, the reference distribution you mention (Poky) is ironically enough not Yocto Project Compatible. For the zedboard I need to linux systems a CentOSx6.4 x86_64 for the xilinx tools and a Fedora18x86_64 for yocto. I build my system with a liveDVD and with cobbler over the network. Are you knowledgeable in git, Linux kernel, and general Linux? What processor are you looking to build for? Is your application for a real time application or just embedded? With yocto you download the software and cross compile for you processor. You can call me at 915-595-1613 or 915-346-1476. I am located in El Paso Tex MST. My other e-mail is devel...@sbcglobal.net. If you want more information let me I can send my resume and cover letter. Regards On Wed, Oct 23, 2013 at 1:47 PM, Chris Morgan chmor...@gmail.com wrote: Hello. We are looking at using Angstrom and bitbake. There are several areas where we could use an expert that could both consult on questions and approaches as well as help implement some of the customization that we may need to ship product. This might start out as a several hour contract, phone or email consultation, and extend to a handful of weeks. We are located in the Boston area but remote is fine. If you might be interested please send me a short email letting me know what your rate would be, a little about your background and some way to get in touch. Chris ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] v2013.06 and v2013.12 architecture change for ARMv7A machines
On 10/27/2013 12:53 PM, Koen Kooi wrote:
On Wed, 2013-10-23 at 18:30 +0200, Björn Krombholz wrote:
On 10/20/2013 09:04 PM, Koen Kooi wrote:
Then I noticed that the 'genericarmv7a' machine in meta-linaro set
the DEFAULTTUNE to armv7athf-neon. A MACHINE config shouldn't set
that variable, but that's a different bug. It turns out that using
that tune we can have a single feed again for all armv7a machines.
Hi,
just for clarification, I'm not sure where to set it if not in the
MACHINE config without modifying meta-angstrom.
I've seen you added MACHINE specific DEFAULTTUNEs based on the currently
supported boards.
Basically the result should be (IMHO):
if MACHINE is a armv7a based and DISTRO is angstrom, then
DEFAULTTUNE = armv7athf-neon
Would it be possible to add those definitions based on SOC_FAMILY:
DEFAULTTUNE_ti33x and DEFAULTTUNE_omap3?
I hope so, see below.
As of now, when I add a new MACHINE=machfoo based on ti33x.inc from
meta-ti, I end up with a DEFAULTTUNE=armv7a-neon instead of the new one,
as the board is not known in meta-angstrom.
I added
DEFAULTTUNE_machfoo = ${DEFAULTTUNE_genericarmv7a}
to the machfoo.conf which is discouraged, if I understand you correctly.
Maybe I'm just missing the obvious safe way?
There is no obvious safe way :( You are running into the same problems
Khem and I ran into with the oe-core way of doing tune files.
This is a big problem and needs to get fixed somehow.
Can we get a good description of the problem in the Yocto Project Bugzilla?
Philip
regards,
Koen
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
