On 23-09-15 12:09, Daniel. wrote:
I think that sync just flushes data to disk and umount clears the dirty bit.
There is no sync.vfat that I know.
Em 23/09/2015 05:31, "Paul D. DeRocco" > escreveu:
> From: Mike Looijmans
>
>
On 24-09-15 08:04, Johannes Pointner wrote:
I'm using autofs to do the trick. It's working fine for me.
To get the umount working I use a timeout of 2 seconds, which seems to
be ok so far.
I am very very interested in how you got that to actually work. Please show us
your configuration
I have to admit, I don't use systemd at the embedded system, but I use
the following files to do it for the usb flash drives:
/etc/auto.master:
+auto.master
/var/autofs /etc/auto.usb --timeout=2
/etc/auto.usb:
usb1-fstype=vfat,rw,sync,noatime,nodiratime,nodev,nosuid,noexec,uid=1000
This may just be 'the way it is', but the stock Fido/BeagleBoneBlack BSP
[core-image-minimal] builds the am335x-boneblack dtb file, and creates in
build/tmp/deploy/images/beaglebone a symlink named
'zImage-am335x-boneblack.dtb'. However - and this is borne out by
README.hardware - uboot is set up
Hello Paul,
I'm using autofs to do the trick. It's working fine for me.
To get the umount working I use a timeout of 2 seconds, which seems to
be ok so far.
Regards,
Hannes
2015-09-23 21:28 GMT+02:00 Daniel. :
> I agree with you that is intrinsically unworkable, if
On my 'to do' list is pulling together the fs partitions into a single SD
card image file that can be copied in-one using a Windows tool (such as
Win32 Disk Imager) - primarily because my build machine is off-site.
I've seen a few recipes along those lines (I'm on a BeagleBone), but perhaps
wic
Hi Daniel,
> I didn't know about this EXTRA_USERS_PARAMS. What I do is adding this
> function to
> my image.
> # This function sets the password for root based on ROOT_PASSWD variable
> set_root_password () {
> local p=$(openssl passwd -1 -salt "My salt" "${ROOT_PASSWD}")
>sed
Hello,
Looking around the web and reading the assorted documents it seems to be
that the defined way to set the root password is to remove "debug-tweaks"
from EXTRA_IMAGE_FEATURES and to add the following lines to local.conf:
require conf/distro/include/security_flags.inc
INHERIT += "extrausers"
Hey Andy,
I didn't know about this EXTRA_USERS_PARAMS. What I do is adding this
function to
my image.
# This function sets the password for root based on ROOT_PASSWD variable
set_root_password () {
local p=$(openssl passwd -1 -salt "My salt" "${ROOT_PASSWD}")
sed -e
Still, I think is a good ideia to understand what is going wrong with
EXTRA_USERS_PARAMS, other users may having the same problem.
Regards,
- dhs
2015-09-24 11:16 GMT-03:00 Daniel. :
> My image .class file has includes a lot of recipes that I wrote for
> specific reasons
My image .class file has includes a lot of recipes that I wrote for
specific reasons so it will not work as it is for you without that recipes,
instead here is the minimal you may need to get this working. I use a class
file because I have lot of images differing in little things, like which
Hi Alex
Thanks for the reply.. very kind! I debugged the plugin using the its Eclipse
SDK and found that the Pluginis using the sdk's folder's name to determine the
host architecture and fails without any warning/hint if the sdk folder can not
be found or follows a different naming convention.
It's installed into /boot on the rootfs with the zImage prefix, and
update-alternatives creates a symlink to the correct path so uboot can find
it. Not sure why this indirection exists, but it does work.
On Thu, Sep 24, 2015 at 4:52 AM Colin Helliwell <
colin.helliw...@ln-systems.com> wrote:
>
Hmmm, ok – maybe I should be baking beyond ‘core-image-minimal’?
As background:
Up until now I’ve just been manually copying/renaming/extracting the various
items - rootfs,modules,kernel,dtb,MLO,uboot - from
build/tmp/deploy/images/beaglebone into the necessary places on SD card. i.e.
that
Hi Andy, Daniel
On Thursday, September 24, 2015 11:20:37 AM Daniel. wrote:
> Still, I think is a good ideia to understand what is going wrong with
> EXTRA_USERS_PARAMS, other users may having the same problem.
EXTRA_USERS_PARAMS works for me all the time. The stanza is what I am using in
my
Actually, that’s incorrect – the stock Fido ‘core-image-mininal’ *doesn’t* put
the kernel into the rootfs tarball either (It’s my own modified configuration
that I’ve added that to).
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org] On
Behalf Of Colin Helliwell
Ah, ok – I see what you mean now. ‘core-image-base’ puts the dtb and kernel
(with symlinks) into /boot in the rootfs tarball.
Thanks for the pointer – that may get me moving onwards again now…
From: Christopher Larson [mailto:clar...@kergoth.com]
Sent: 24 September 2015 15:27
To:
We have an automated build which pulls our own layers & amendments from our
version control system. We don't really want (need?) to have a full
*unpacked* Yocto in the repository too, so we have just the Fido tarball in
there, and unpack this as the first step of the build.
But, we then need to
On 2015-09-24 09:45, Colin Helliwell wrote:
We have an automated build which pulls our own layers & amendments from our
version control system. We don’t really want (need?) to have a full *unpacked*
Yocto in the repository
too, so we have just the Fido tarball in there, and unpack this as the
Thanks Gary - I'll give that a try, looks like just what I'm after.
-Original Message-
From: yocto-boun...@yoctoproject.org [mailto:yocto-boun...@yoctoproject.org]
On Behalf Of Gary Thomas
Sent: 24 September 2015 16:56
To: yocto@yoctoproject.org
Subject: Re: [yocto] Getting bitbake to use
Rudi wrote
> > Still, I think is a good ideia to understand what is going wrong with
> > EXTRA_USERS_PARAMS, other users may having the same problem.
>
> EXTRA_USERS_PARAMS works for me all the time. The stanza is what I am
using
> in my image recipes:
>
> EXTRA_USERS_PARAMS = "\
> groupadd
Many buildsets pull in meta-qt3 but don't use it, so remove the layer from those
buildsets.
Signed-off-by: Ross Burton
---
buildset-config.controller/nightly-arm.conf | 3 ---
buildset-config.controller/nightly-arm64.conf| 3 ---
The autobuilder was specifying the test list explicitly in several buildsets
because in the past the SMART and RPM tests didn't skip automatically on non-RPM
images. However we're removing the dmesg test as it is obsolete (replaced by
parselogs) but the autobuilder still attempts to run it.
Now
There are patches for oe-core which improve the behaviour of multilib images but
show that the RPM-based multilib image construction was working more by luck
than anything else.
Explicitly set RPM_PREFER_ARCH_ELF="1" to prefer 32-bit binaries when both
options are being installed.
Signed-off-by:
Hello!
This series of patches adds support for Axxia's ARM and ARM64 platforms
on linux-yocto-4.1. Below there is a summary on the commits.
Please create 2 axxia branches
- one based on standard/base, preferably named "standard/axxia/base"
- one based on standard/preempt-rt, preferably named
>
> What are the rules with appending included recipes?
>
File inclusions with include or require are literal: the content of the
referenced file is inserted at the very position of the statement. The file
extension is irrelevant, meaning any appends to a recipe do not get
included.
:rjs
--
How can I create an empty directory in my root FS? I want to create
/mnt/sd to use as a mount point. I put "install -d ${D}/mnt/sd" in
do_install() of one of my recipes, but I get:
ERROR: QA Issue: my-recipe: Files/directories were installed but not shipped
/mnt
/mnt/sd
i'm completly new to yocta and doing my first steps.
plan is to build a system with a small footprint for low-latency video
wifibroadcast.
first steps are trying to build rpi-test-image including omxplayer. but
compiling fails when compiling userland.
last lines before the failure are. am
Hello,
I am working with a BSP that has multiple image recipes.
foo-hwbringup-image.bb
foo-qt5demo-image.bb
foo-qt5demo-image.bb contains "require foo-hwbringup-image.bb"
However if I create foo-hwbringup-image.bbappend, it gets ignored.
What are the rules with appending included recipes?
On 09/24/2015 03:25 PM, Cristian Bercaru wrote:
Hello!
This series of patches adds support for Axxia's ARM and ARM64 platforms
on linux-yocto-4.1. Below there is a summary on the commits.
Please create 2 axxia branches
- one based on standard/base, preferably named "standard/axxia/base"
- one
On 25 September 2015 at 10:32, Edward Wingate wrote:
>
> How can I create an empty directory in my root FS? I want to create
> /mnt/sd to use as a mount point. I put "install -d ${D}/mnt/sd" in
> do_install() of one of my recipes, but I get:
>
> ERROR: QA Issue: my-recipe:
Can you try the patches from
https://github.com/kraj/meta-raspberrypi/commits/kraj/master
On Thu, Sep 24, 2015 at 4:19 PM, Tom Martin wrote:
> i'm completly new to yocta and doing my first steps.
>
> plan is to build a system with a small footprint for low-latency video
>
32 matches
Mail list logo