] in kernel manual, should pick another example for
KMACHINE
On Thu, Mar 5, 2015 at 10:03 PM, Robert P. J. Day rpj...@crashcourse.ca
wrote:
in section 3.2 of the kernel dev manual, there is a discussion of
KMACHINE and how it is *typically* set to the same value as MACHINE,
but there are cases where
,
Scott
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-
boun...@yoctoproject.org] On Behalf Of Nathan Rossi
Sent: Thursday, March 05, 2015 5:48 AM
To: Robert P. J. Day
Cc: Yocto discussion list
Subject: Re: [yocto] in kernel manual, should pick another example
KMACHINE value?
Scott
-Original Message-
From: Robert P. J. Day [mailto:rpj...@crashcourse.ca]
Sent: Thursday, March 05, 2015 9:15 AM
To: Rifenbark, Scott M
Cc: Nathan Rossi; Yocto discussion list
Subject: RE: [yocto] in kernel manual, should pick another example for
KMACHINE
On Thu, 5 Mar
On Thu, 5 Mar 2015, Rifenbark, Scott M wrote:
I like Nathan's suggestion for the text. Can someone explain to me
though why emenlow is not a good example here? In the
linux-yocto_3.14.bbappend file, KMACHINE_emenlow-noemgd is set equal
to emenlow. Isn't this equating emenlow-noemgd and
On Thu, Mar 5, 2015 at 10:03 PM, Robert P. J. Day rpj...@crashcourse.ca wrote:
in section 3.2 of the kernel dev manual, there is a discussion of
KMACHINE and how it is *typically* set to the same value as MACHINE,
but there are cases where that might not be true; however, the example
used
in section 3.2 of the kernel dev manual, there is a discussion of
KMACHINE and how it is *typically* set to the same value as MACHINE,
but there are cases where that might not be true; however, the example
used to demonstrate this -- emenlow and emenlow-noemgd -- doesn't seem
appropriate as