diff --git a/documentation/bsp-guide/bsp.xml b/documentation/bsp-guide/bsp.xml index e2262a41f8..3cda0f6b70 100644 --- a/documentation/bsp-guide/bsp.xml +++ b/documentation/bsp-guide/bsp.xml @@ -902,8 +902,15 @@ recipes-bsp, recipes-graphics, recipes-core, and so forth). - Place the BSP-specific files in the directory named for - your machine inside the BSP layer. + Place the BSP-specific files in the proper directory + inside the BSP layer. + How expansive the layer is affects where you must place these files. + For example, if your layer supports several different machine types, + you need to be sure your layer's directory structure includes hierarchy + that separates the files out according to machine. + If your layer does not support multiple machines, the layer would not + have that additional hierarchy and the files would obviously not be + able to reside in a machine-specific directory. @@ -912,7 +919,8 @@ Following is a specific example to help you better understand the process. Consider an example that customizes a recipe by adding a BSP-specific configuration file named interfaces to the - init-ifupdown_1.0.bb recipe for machine "xyz". + init-ifupdown_1.0.bb recipe for machine "xyz" where the + BSP layer also supports several other machines. Do the following: Edit the init-ifupdown_1.0.bbappend file so that it @@ -926,8 +934,17 @@ Create and place the new interfaces configuration file in the BSP's layer here: - meta-xyz/recipes-core/init-ifupdown/files/xyz/interfaces + meta-xyz/recipes-core/init-ifupdown/files/xyz-machine-one/interfaces + + If the meta-xyz layer did not support + multiple machines, you would place the + interfaces configuration file in the + layer here: + + meta-xyz/recipes-core/init-ifupdown/files/interfaces + + The FILESEXTRAPATHS variable in the append files extends the search path