a IPv6
link local address.
If someone has a solution using just /etc/network/interface based settings I
would be interested to hear it.
Regards, Thomas Thorne
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo
> > FWIW: We created a proprietary license file called files/common-
> > licenses/company.txt in our proprietary layer, then added the
> > following to layer.conf:
> >
> > COMPANY_COMMON_LICENSES := '${@os.path.normpath("${LAYERDIR}/files
> > /com
> > mon-licenses")}'
> >
Good afternoon,
I am trying to generate an image for a Raspberry Pi 3 that includes a
`/etc/network/interfaces` file which causes the Pi to start with an "up" eth0
connection with only an IPv6 link local address.
The Pi will be connected to an active switch on boot so the copper ethernet
>> Is it only possible to use the special
>> LICENSE = "CLOSED"
>> license for licenses not already placed in the main license directory?
>
> Yes, there's special-case logic for 'CLOSED'. Can you not just use that for
> your internal pieces? It's special-cased in a few places.
I can use
? Now when I fire a bitbake command like "bitbake test" all the packages
listed into the recipe get build. But sometime I need to build only one package
say test1.
?
? How that can be achieved as when I tried "bitbake test1" its reports below
error
? ERROR: Nothing PROVIDES test1'
I
Obviously I was having some trouble when I created this work area:
~/work/yocto-rpi/meta-raspberrypi$ git branch -l
krogoth
* master
origin/krogoth
origon/krogoth
origonkrogoth
So I delete all those and try:
$ git checkout origin/krogoth
warning: refname 'origin/krogoth' is ambiguous.
Thank you for your assistance. The final recipe I used looks like this:
#
# Copy the ppp script files for chips to the target filesystem
# These files are based on the details provided in
#
SUMMARY = "PPP Scripts for Basic Chip Operation"
SECTION = "net"
LICENSE = "MIT"
LIC_FILES_CHKSUM =
"
To:
IMAGE_FSTYPES = "tar.xz ext3"
Is this a bug I should raise on the
https://github.com/agherzan/meta-raspberrypi/ project or am I missing some step?
I take it there might be a handful of variables I need to set before it is safe
to use the rpi-sdimg in my configuration now?
I updated my Krogoth work area today with `git pull` and I now seeing error
messages about being unable to open a root filesystem image for a raspberrypi3.
I have tried in my build area that tries to make an SD card image and the
default one which does whatever the basic setup is.
Output from
ware. Thank you for the warning though.
Thomas A. F. Thorne<mailto:thomas.tho...@net2edge.com> Software Engineer
Net2Edge<http://www.net2edge.com/>
From: Bruce Ashfield [mailto:bruce.ashfi...@gmail.com]
Sent: 10 November 2016 15:19
To: Thomas Thorne <thomas.tho...@net2edge.com>
C
May have solved the issue. Thank you for your help.
> What do you get from this?
>% bitbake rpi-test-image -e | grep ^IMAGE_FSTYPES
I get:
thomasthorne@thorne-ul-dt:~/work/rpi-layer/build$ bitbake rpi-test-image -e |
grep ^IMAGE_FSTYPES
IMAGE_FSTYPES_DEBUGFS="tar.xz ext3"
> Do you see an image with .rpi-sdimg in deploy/images/raspberrypi3
No, files such as that not turning up is exactly what I am asking about.
thomasthorne@thorne-ul-dt:~/work/rpi-layer/build$ ls
tmp/deploy/images/raspberrypi3/*.rpi-sdimg
ls: cannot access
12 matches
Mail list logo
