I would like to point out the reason CROSS_COMPILE is used is because
kernel makes things that run natively and also things that are for the
end environment. Thus $(CROSS_COMPILE)$(CXX) is used to prepend when
building something for the end system, and $(CXX) is used for local run
items. So even
While, I'm not an expert, I would like to point out:
http://kernel.org/doc/index-old.html (the new index references this but
the information isn't on the new index page directly).
One thing mentioned is that a make distclean is required for reasonable
results between any run with different archite
The kernel is a special case, where the SDK is really designed for
developing user applications (which the kernel is not).
I found it pretty easy to create a kernel-module-MYMODULE.bbclass file
and build the kernel and module in the OE/Poky build system directly,
and then have it included in the i
Or better yet, now that it is past initial, use
http://www.yoctoproject.org/docs/1.4/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules.
:)
It worked fine for 1.2 (denzil) for me, though it is written for a later
one.
Brian
On Tue, 2013-01-15 at 11:07 -0600, Brian Lloyd wrote:
>
Try this in work documentation and let us know how it helps or if there
is something missing that would help more:
http://www.yoctoproject.org/docs/hart/kernel-dev/kernel-dev.html#incorporating-out-of-tree-modules
I just did the exact same thing and was happy to discover there is
support in yocto
I don't think it is just the intel ones. All the BSPs I've looked at
had this problem.
The yocto-bsp also creates packages that add to the problem, as it's
finished product adds files that end up in every BSP, and the final
source selected is not dependent on the machine. (userpatches and
userco
>From the perspective of a new, easily confused and overwhelmed user, I
whole heartedly agree with the index entry. And now it makes sense why
there is a PV to store version of a recipe.
On Fri, 2012-09-28 at 18:46 +, Rifenbark, Scott M wrote:
> Rudolf,
>
>
>
> This is good feedback on
;
> -Original Message-
> From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
> On Behalf Of Burton, Ross
> Sent: Tuesday, September 25, 2012 10:00 AM
> To: Brian Lloyd
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Documentation clarification
should
KERNEL_FEATURES_append_qemux86="cfg/sound"
have a space between the " and c?
My understanding is that append does a straight append with no added
whitespace, so that would cause the line to become something like
"feature/neatfeaturecfg/sound", which I don't understand how could be
ri
Simple: tags aren't guaranteed to not change what it references, the
hash is guaranteed to always point to the same thing. Thus, git is
double checking that the meaning of the tag hasn't changed.
On Thu, 2012-09-20 at 16:32 -0400, William Mills wrote:
> On 09/20/2012 04:08 PM, Evade Flow wrote:
FYI: I've been using linux-yocto 3.2. After doing a git pull recently,
I found both my own BSP and crownbay-noemgd to be miss configured, both
for linux-yocto and for xorg.conf, like it couldn't find the
configuration files. I think the root problem with files not being
found may be a little larg
Tue, Sep 18, 2012 at 12:04 PM, Trevor Woerner wrote:
> > On Tue, Sep 18, 2012 at 2:23 PM, Brian Lloyd wrote:
> >> Most of my hits for such an item
> >> discuss the packages I will need to install in my host distribution so I
> >> can use the yocto project
I took a look at the mega-manual for the first time after hearing
mention of it in the meeting.
>From a new user perspective, it seems a step backwards. While
everything may be there, it has the needle in the haystack feeling. The
only way to find something is to search for it, but what search t
FYI: new user stuck having to implement a bps found the description below about
the extra demarcation between groups and partitions helpful. Now if only I
knew which branches were partitions and which where groups...
Brian A Lloyd
On Aug 21, 2012, at 12:14 PM, Darren Hart wrote:
> On 08/20
14 matches
Mail list logo
