* enable netbase network interfaces?
@ 2012-12-25 23:31 Lai Eddy
2012-12-26 12:08 ` Gary Thomas
0 siblings, 1 reply; 6+ messages in thread
From: Lai Eddy @ 2012-12-25 23:31 UTC (permalink / raw)
To: Yocto discussion list
[-- Attachment #1: Type: text/plain, Size: 800 bytes --]
in the "Reference Manual "How do I make sure connected network interfaces
are brought up by default?" said 2 files need to be added to enable
network interfaces, where can I find template files?
-----------------------------------------------------------------------------------------------------------
The default interfaces file provided by the netbase recipe does not
automatically bring up network interfaces. Therefore, you will need to add
a BSP-specific netbase that includes an interfaces file.
For example, add the following files to your layer:
meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces
meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend
------------------------------------------------------------------------------------------------------------
[-- Attachment #2: Type: text/html, Size: 1008 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: enable netbase network interfaces? 2012-12-25 23:31 enable netbase network interfaces? Lai Eddy @ 2012-12-26 12:08 ` Gary Thomas 2012-12-28 6:40 ` Lai Eddy 0 siblings, 1 reply; 6+ messages in thread From: Gary Thomas @ 2012-12-26 12:08 UTC (permalink / raw) To: yocto On 2012-12-25 16:31, Lai Eddy wrote: > in the "Reference Manual "How do I make sure connected network interfaces are brought up by default?" said 2 files need to be added to enable network interfaces, where can I find > template files? > ----------------------------------------------------------------------------------------------------------- > The default interfaces file provided by the netbase recipe does not automatically bring up network interfaces. Therefore, you will need to add a BSP-specific netbase that includes > an interfaces file. > For example, add the following files to your layer: > meta-MACHINE/recipes-bsp/netbase/netbase/MACHINE/interfaces > meta-MACHINE/recipes-bsp/netbase/netbase_5.0.bbappend > ------------------------------------------------------------------------------------------------------------ Look in meta-ti (git://git.yoctoproject.org/meta-ti): $ find meta-ti/recipes-core/netbase/ meta-ti/recipes-core/netbase/ meta-ti/recipes-core/netbase/netbase-5.0 meta-ti/recipes-core/netbase/netbase-5.0/beagleboard meta-ti/recipes-core/netbase/netbase-5.0/beagleboard/interfaces meta-ti/recipes-core/netbase/netbase_5.0.bbappend -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: enable netbase network interfaces? 2012-12-26 12:08 ` Gary Thomas @ 2012-12-28 6:40 ` Lai Eddy 2012-12-28 14:38 ` Gary Thomas 0 siblings, 1 reply; 6+ messages in thread From: Lai Eddy @ 2012-12-28 6:40 UTC (permalink / raw) To: Gary Thomas; +Cc: yocto [-- Attachment #1: Type: text/plain, Size: 1877 bytes --] Thanks Gary, after download and extract the ti cortex A8 BSP . there's only binary image inside, what MACHINE to use to build a beagleboard yocto image? On 2012-12-25 16:31, Lai Eddy wrote: > in the "Reference Manual "How do I make sure connected network interfaces > are brought up by default?" said 2 files need to be added to enable network > interfaces, where can I find > template files? > ------------------------------**------------------------------** > ------------------------------**----------------- > The default interfaces file provided by the netbase recipe does not > automatically bring up network interfaces. Therefore, you will need to add > a BSP-specific netbase that includes > an interfaces file. > For example, add the following files to your layer: > meta-MACHINE/recipes-bsp/**netbase/netbase/MACHINE/**interfaces > meta-MACHINE/recipes-bsp/**netbase/netbase_5.0.bbappend > ------------------------------**------------------------------** > ------------------------------**------------------ > Look in meta-ti (git://git.yoctoproject.org/**meta-ti<http://git.yoctoproject.org/meta-ti> ): $ find meta-ti/recipes-core/netbase/ meta-ti/recipes-core/netbase/ meta-ti/recipes-core/netbase/**netbase-5.0 meta-ti/recipes-core/netbase/**netbase-5.0/beagleboard meta-ti/recipes-core/netbase/**netbase-5.0/beagleboard/**interfaces meta-ti/recipes-core/netbase/**netbase_5.0.bbappend -- ------------------------------**------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------**------------------------------ ______________________________**_________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.**org/listinfo/yocto<https://lists.yoctoproject.org/listinfo/yocto> [-- Attachment #2: Type: text/html, Size: 2441 bytes --] ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: enable netbase network interfaces? 2012-12-28 6:40 ` Lai Eddy @ 2012-12-28 14:38 ` Gary Thomas 2012-12-29 9:58 ` Robert P. J. Day 0 siblings, 1 reply; 6+ messages in thread From: Gary Thomas @ 2012-12-28 14:38 UTC (permalink / raw) To: Lai Eddy; +Cc: yocto On 2012-12-27 23:40, Lai Eddy wrote: > Thanks Gary, > > after download and extract the ti cortex A8 BSP . there's only binary image inside, what MACHINE to use to build a beagleboard yocto image? MACHINE="beagleboard" Why does this matter? You asked about how to set up *your* BSP to have a tailored network interface file. All you need to do is pattern your setup after the beagleboard one, as quoted. n.b. please don't top-post :-( > > On 2012-12-25 16:31, Lai Eddy wrote: > > in the "Reference Manual "How do I make sure connected network interfaces are brought up by default?" said 2 files need to be added to enable network interfaces, where can I find > template files? > ------------------------------__------------------------------__------------------------------__----------------- > The default interfaces file provided by the netbase recipe does not automatically bring up network interfaces. Therefore, you will need to add a BSP-specific netbase that includes > an interfaces file. > For example, add the following files to your layer: > meta-MACHINE/recipes-bsp/__netbase/netbase/MACHINE/__interfaces > meta-MACHINE/recipes-bsp/__netbase/netbase_5.0.bbappend > ------------------------------__------------------------------__------------------------------__------------------ > > > Look in meta-ti (git://git.yoctoproject.org/__meta-ti <http://git.yoctoproject.org/meta-ti>): > $ find meta-ti/recipes-core/netbase/ > meta-ti/recipes-core/netbase/ > meta-ti/recipes-core/netbase/__netbase-5.0 > meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard > meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard/__interfaces > meta-ti/recipes-core/netbase/__netbase_5.0.bbappend > > > > -- > ------------------------------__------------------------------ > Gary Thomas | Consulting for the > MLB Associates | Embedded world > ------------------------------__------------------------------ > _________________________________________________ > yocto mailing list > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > https://lists.yoctoproject.__org/listinfo/yocto <https://lists.yoctoproject.org/listinfo/yocto> -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: enable netbase network interfaces? 2012-12-28 14:38 ` Gary Thomas @ 2012-12-29 9:58 ` Robert P. J. Day 2012-12-29 12:25 ` Gary Thomas 0 siblings, 1 reply; 6+ messages in thread From: Robert P. J. Day @ 2012-12-29 9:58 UTC (permalink / raw) To: Gary Thomas; +Cc: yocto On Fri, 28 Dec 2012, Gary Thomas wrote: > On 2012-12-27 23:40, Lai Eddy wrote: > > Thanks Gary, > > > > after download and extract the ti cortex A8 BSP . there's only binary image > > inside, what MACHINE to use to build a beagleboard yocto image? > > MACHINE="beagleboard" > > Why does this matter? You asked about how to set up *your* BSP to have > a tailored network interface file. All you need to do is pattern your > setup after the beagleboard one, as quoted. > > n.b. please don't top-post :-( > > > > > On 2012-12-25 16:31, Lai Eddy wrote: > > > > in the "Reference Manual "How do I make sure connected network > > interfaces are brought up by default?" said 2 files need to be added to > > enable network interfaces, where can I find > > template files? > > ------------------------------__------------------------------__------------------------------__----------------- > > The default interfaces file provided by the netbase recipe does not > > automatically bring up network interfaces. Therefore, you will need to add a > > BSP-specific netbase that includes > > an interfaces file. > > For example, add the following files to your layer: > > meta-MACHINE/recipes-bsp/__netbase/netbase/MACHINE/__interfaces > > meta-MACHINE/recipes-bsp/__netbase/netbase_5.0.bbappend > > ------------------------------__------------------------------__------------------------------__------------------ > > > > > > Look in meta-ti (git://git.yoctoproject.org/__meta-ti > > <http://git.yoctoproject.org/meta-ti>): > > $ find meta-ti/recipes-core/netbase/ > > meta-ti/recipes-core/netbase/ > > meta-ti/recipes-core/netbase/__netbase-5.0 > > meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard > > meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard/__interfaces > > meta-ti/recipes-core/netbase/__netbase_5.0.bbappend i'm not sure where your "__" prefixes are coming from, but i know i've pointed out before that meta-ti's netbase_5.0.bbappend file seems to be broken. currently, on dev branch, it contains: THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:" that value for FILESPATH is incorrect -- because the directory name for the "interfaces" file in meta-ti is netbase-5.0 (not simply netbase), it will *not* be picked up; rather, the default "interfaces" file from oe-core will be pulled in. using bitbake-env, you can *see* the FILESPATH value that's used when building for beagle using meta-ti: $ bitbake-env -r netbase FILESPATH | tr : '\n' Parsing recipes..WARNING: No recipes available for: /home/rpjday/oe/dist/layers/meta-ti/recipes-graphics/mesa/mesa-dri_8.0.4.bbappend done. # FILESPATH="${@base_set_filespath(["${THISDIR}/${PN}"], d)} ${@base_set_filespath(["${FILE_DIRNAME}/${BP}", "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}" FILESPATH="/home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/arm /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/beagleboard /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/omap3 /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/ /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/beagleboard /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/omap3 /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/beagleboard /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/omap3 /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/arm /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/beagleboard /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/omap3 /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/ /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/" $ you can see that FILESPATH doesn't include the very directory in meta-ti that contains the overriding beagleboard "interfaces" file. or am i horribly misunderstanding something here? rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ======================================================================== ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: enable netbase network interfaces? 2012-12-29 9:58 ` Robert P. J. Day @ 2012-12-29 12:25 ` Gary Thomas 0 siblings, 0 replies; 6+ messages in thread From: Gary Thomas @ 2012-12-29 12:25 UTC (permalink / raw) To: Robert P. J. Day; +Cc: yocto On 2012-12-29 02:58, Robert P. J. Day wrote: > On Fri, 28 Dec 2012, Gary Thomas wrote: > >> On 2012-12-27 23:40, Lai Eddy wrote: >>> Thanks Gary, >>> >>> after download and extract the ti cortex A8 BSP . there's only binary image >>> inside, what MACHINE to use to build a beagleboard yocto image? >> >> MACHINE="beagleboard" >> >> Why does this matter? You asked about how to set up *your* BSP to have >> a tailored network interface file. All you need to do is pattern your >> setup after the beagleboard one, as quoted. >> >> n.b. please don't top-post :-( >> >>> >>> On 2012-12-25 16:31, Lai Eddy wrote: >>> >>> in the "Reference Manual "How do I make sure connected network >>> interfaces are brought up by default?" said 2 files need to be added to >>> enable network interfaces, where can I find >>> template files? >>> ------------------------------__------------------------------__------------------------------__----------------- >>> The default interfaces file provided by the netbase recipe does not >>> automatically bring up network interfaces. Therefore, you will need to add a >>> BSP-specific netbase that includes >>> an interfaces file. >>> For example, add the following files to your layer: >>> meta-MACHINE/recipes-bsp/__netbase/netbase/MACHINE/__interfaces >>> meta-MACHINE/recipes-bsp/__netbase/netbase_5.0.bbappend >>> ------------------------------__------------------------------__------------------------------__------------------ >>> >>> >>> Look in meta-ti (git://git.yoctoproject.org/__meta-ti >>> <http://git.yoctoproject.org/meta-ti>): >>> $ find meta-ti/recipes-core/netbase/ >>> meta-ti/recipes-core/netbase/ >>> meta-ti/recipes-core/netbase/__netbase-5.0 >>> meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard >>> meta-ti/recipes-core/netbase/__netbase-5.0/beagleboard/__interfaces >>> meta-ti/recipes-core/netbase/__netbase_5.0.bbappend > > i'm not sure where your "__" prefixes are coming from, but i know > i've pointed out before that meta-ti's netbase_5.0.bbappend file seems > to be broken. currently, on dev branch, it contains: > > THISDIR := "${@os.path.dirname(bb.data.getVar('FILE', d, True))}" > FILESPATH =. "${@base_set_filespath(["${THISDIR}/${PN}"], d)}:" > > that value for FILESPATH is incorrect -- because the directory name > for the "interfaces" file in meta-ti is netbase-5.0 (not simply > netbase), it will *not* be picked up; rather, the default "interfaces" > file from oe-core will be pulled in. > > using bitbake-env, you can *see* the FILESPATH value that's used > when building for beagle using meta-ti: > > $ bitbake-env -r netbase FILESPATH | tr : '\n' > Parsing recipes..WARNING: No recipes available for: > > /home/rpjday/oe/dist/layers/meta-ti/recipes-graphics/mesa/mesa-dri_8.0.4.bbappend > done. > # FILESPATH="${@base_set_filespath(["${THISDIR}/${PN}"], d)} > ${@base_set_filespath(["${FILE_DIRNAME}/${BP}", > "${FILE_DIRNAME}/${BPN}", "${FILE_DIRNAME}/files"], d)}" > FILESPATH="/home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/arm > /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/beagleboard > /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/omap3 > /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/armv7a > /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/ > /home/rpjday/oe/dist/layers/meta-ti/recipes-core/netbase/netbase/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/arm > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/beagleboard > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/omap3 > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/armv7a > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase-5.0/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/arm > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/beagleboard > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/omap3 > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/armv7a > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/netbase/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/arm > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/beagleboard > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/omap3 > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/armv7a > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/ > /home/rpjday/oe/dist/layers/oe-core/meta/recipes-core/netbase/files/" > $ > > you can see that FILESPATH doesn't include the very directory in > meta-ti that contains the overriding beagleboard "interfaces" file. > > or am i horribly misunderstanding something here? I agree that file is incorrect. I simply quoted its use as it is the only example in a commonly available layer. I'll send a patch for the meta-ti file and hopefully they'll fix it. Here's what I use in my own layers [which are not public, sorry] $ cat meta-some-target/recipes-core/netbase/netbase_5.0.bbappend FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:" PACKAGE_ARCH = "${MACHINE_ARCH}" This will pick up the interfaces file from ".../meta-some-target/recipes-core/netbase/netbase-5.0/${MACHINE}/interfaces" As for the "__" scattered in the email - those crept in with Eddy's reply. -- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2012-12-29 12:25 UTC | newest] Thread overview: 6+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2012-12-25 23:31 enable netbase network interfaces? Lai Eddy 2012-12-26 12:08 ` Gary Thomas 2012-12-28 6:40 ` Lai Eddy 2012-12-28 14:38 ` Gary Thomas 2012-12-29 9:58 ` Robert P. J. Day 2012-12-29 12:25 ` Gary Thomas
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.