Re: [yocto] systemd - how do I wait for a driver to load?

[Sven Ebenfeld]

Am 26.08.2014 22:51, schrieb Chris Tapp:
> 
> On 26 Aug 2014, at 21:02, Sven Ebenfeld  wrote:
> 
>> You should look at  "ConditionPathExists=" Options of systemd-units.
> 
> Thanks, that looks like it would do the job. I was hoping not to hard code 
> paths as they may change if a configuration file is changed, but...
> 
>> Otherwise if udev is loading your device module, you could add the
>> device-unit to "Requires=" option.
> 
> This sounds better. Is there an easy way to tell if udev did load the module? 
> There's nothing obvious in the syslog.

If you didn't load the module by hand it's probably udev. If you didn't
run modprobe or insmod. Then you should try to create a device-unit for
the device.

For /dev/dvb/adaptor the unit should probably be something like
dev-dvb-adaptor.device .

> 
>> Am 26.08.2014 21:52, schrieb Chris Tapp:
>>> I've got a service running under systemd that will only start once a kernel 
>>> module has loaded and created its /dev/dvb/adaptor nodes.
>>>
>>> Unfortunately, it doesn't load until after the service has failed and gone 
>>> into an error state due to too many restarts.
>>>
>>> I could "fix" this by increasing the restart interval, but is there a way 
>>> of adding a dependancy on the kernel module?
>>>
>>> --
>>>
>>> Chris Tapp
>>> opensou...@keylevel.com
>>> www.keylevel.com
>>>
>>>
>>>
>>>
> 
> --
> 
> Chris Tapp
> opensou...@keylevel.com
> www.keylevel.com
> 
> 
> 
> 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] building a hierarchical poky variable glossary, noting what's missing

[Robert P. J. Day]

On Tue, 26 Aug 2014, Rifenbark, Scott M wrote:

> Robert,
>
> I can see your link being referenced from the YP ref-manual to
> augment variable descriptions and explanations.  Also, your
> compilation could act as another source of information similar to
> the list of "other information" items that currently are shown at
> the front of the dev-manual.

  this whole thing will come in fits and spurts, and may even be
redesigned completely if i think of a better way but, for the time
being, if you're bored :-), you can always peruse it from time to
time and note the variables that aren't included either in
documentation.conf or the ref manual and do something about them:

http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary

of course, it's impossible to document *every* variable but in some
cases, it's obvious that some variables deserve documentation.

rday

-- 


Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca

Twitter:   http://twitter.com/rpjday
LinkedIn:   http://ca.linkedin.com/in/rpjday


-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Image that depends on another image

[Seth Bollinger]

On Thu, Aug 21, 2014 at 7:25 PM, Christopher Larson 
wrote:

>
> On Thu, Aug 21, 2014 at 5:08 PM, Seth Bollinger 
> wrote:
>
>> Our device requires two images to be built.  Is there any way to have the
>> first image depend on the second image?
>
>
> do_rootfs[depends] += "some-other-image:do_rootfs" would probably do.
>

I hate to resurrect this thread, but after testing this out and using it we
ran into a small hiccup.  Since we're using the second image to generate a
second partition, a lot of the dependencies actually need to be injected
into the first image (users, utilities, etc.).  Is there a way to do this?

Thanks again!

Seth
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Force recipe to provide specific file

[Richard Leitner]

On Fri, 22 Aug 2014 11:07:41 +0200
Anders Darander  wrote:

> 
> > What happens for example if do_install_append is already defined in the 
> > recipe?
> 
> 
> No issue at all. The do_install_append's will just be appended one after
> each other.

Thanks you for this info!

Maybe it would be a good idea to add it to the documentation somewhere ;-)

regards,
richard


signature.asc
Description: PGP signature
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Build dts alone

[Anooj Gopi]

Hello,

After changing the kernel dts file (directly in work directory) I would
like to build just the dtb file from yocto (without rebuilding entire
virtual/kernel target). Is it possible to do so?

Regards,
Anooj
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build dts alone

[Maciej Borzecki]

On Wednesday 27 of August 2014 15:57:40 Anooj Gopi wrote:
> Hello,
> 
> After changing the kernel dts file (directly in work directory) I would
> like to build just the dtb file from yocto (without rebuilding entire
> virtual/kernel target). Is it possible to do so?
First:
bitbake -c devshell virtual/kernel

Within the shell:
make dtbs

Or just build particular dtb if you know the name.

-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you. 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build dts alone

[Anooj Gopi]

Thank you very much... devshell is really cool.

It would be nice if we could mention this info some where in
http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html



On Wed, Aug 27, 2014 at 4:05 PM, Maciej Borzecki <
maciej.borze...@open-rnd.pl> wrote:

> On Wednesday 27 of August 2014 15:57:40 Anooj Gopi wrote:
> > Hello,
> >
> > After changing the kernel dts file (directly in work directory) I would
> > like to build just the dtb file from yocto (without rebuilding entire
> > virtual/kernel target). Is it possible to do so?
> First:
> bitbake -c devshell virtual/kernel
>
> Within the shell:
> make dtbs
>
> Or just build particular dtb if you know the name.
>
> --
>
> Maciej Borzęcki
> Senior Software Engineer Open-RnD Sp. z o.o.
> www.open-rnd.pl, Facebook, Twitter
> mobile: +48 telefon, fax: +48 42 657 9079
>
> Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub
> poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób,
> do
> których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo
> zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim
> przypadku
> uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie
> nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy.
>
> This message, including any attachments hereto, may contain privileged or
> confidential information and is sent solely for the attention and use of
> the
> intended addressee(s). If you are not an intended addressee, you may
> neither
> use this message nor copy or deliver it to anyone. In such case, you should
> immediately destroy this message and kindly notify the sender by reply
> email.
> Thank you.
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Build dts alone

[Maciej Borzecki]

On Wednesday 27 of August 2014 16:12:58 Anooj Gopi wrote:
> Thank you very much... devshell is really cool.
> 
> It would be nice if we could mention this info some where in
> http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html

It is mentioned in developer's manual:
https://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#platdev-appdev-devshell


-- 

Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you. 
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-autobuilder] buildsteps/RunOeSelftest.py: change the way oe-selftest is called

[Flanagan, Elizabeth]

On Wed, Aug 20, 2014 at 5:57 AM, Corneliu Stoicescu
 wrote:
> A recent patch went in poky master that added command line parsing and 
> options to the oe-selftest script.
> Changing the way oe-selftest is called by the autobuilder to account for 
> these changes.
>
> Signed-off-by: Corneliu Stoicescu 
> ---
>  lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git 
> a/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py 
> b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py
> index 0efddd7..3d95583 100644
> --- a/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py
> +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py
> @@ -22,5 +22,5 @@ class RunOeSelftest(ShellCommand):
>  self.description = "Running oe-selftest"
>  self.timeout = 10
>  kwargs['timeout']=self.timeout
> -self.command = "if [ -d meta-selftest ]; then . ./oe-init-build-env; 
> oe-selftest; else echo 'Skipping step - no meta-selftest layer here'; fi"
> +self.command = "if [ -d meta-selftest ]; then . ./oe-init-build-env; 
> oe-selftest --run-all-tests; else echo 'Skipping step - no meta-selftest 
> layer here'; fi"
>  ShellCommand.__init__(self, **kwargs)
> --
> 1.8.3.2
>
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

Pulled into master. Pushing into Production this afternoon. Thanks!

-- 
Elizabeth Flanagan
Yocto Project
Build and Release
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Add the new driver in yocto

[vinod kumar]

Hi,

I am using yocto for wandboard. I have written one I2C driver for my I2C
device.

 *The procedure which I followed to add and build the driver in yocto is as*
:

1) Make the entry of my driver in Makefile and Kconfig in build directory.
2) Replace the defconfig (present in source directory) with .config
(present in build directory).
3) Add the driver information in device tree file.

Then I run the *bitbake linux-imx -c compile -f* to compile the kernel and
face some errors. So is there any way (like to add as a patch *(patch of
conf file and driver source code*) in some .bbappend file or something
equivalent to it) through which I can add and compile my driver successfully

*But during compilation I faced the below errors:*






















































*vinod@vinod:~/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/git$
bitbake linux-imx -c compile -fLoading cache: 100%
||
ETA:  00:00:00Loaded 1820 entries from dependency cache.NOTE: Resolving any
missing task queue dependenciesBuild Configuration:BB_VERSION=
"1.22.0"BUILD_SYS = "x86_64-linux"NATIVELSBSTRING   =
"Ubuntu-12.04"TARGET_SYS= "arm-poky-linux-gnueabi"MACHINE
= "imx6qsabresd"DISTRO= "poky"DISTRO_VERSION=
"1.6.1"TUNE_FEATURES = "armv7a vfp neon callconvention-hard
cortexa9"TARGET_FPU= "vfp-neon"meta  meta-yocto
= "(nobranch):8e05d5e3fe04face623c4f9fb08b12f13c22edab"meta-oe   =
"(nobranch):ee24939c4c70b63a9fb7e93a58889a3231d3d367"meta-fsl-arm  =
"(nobranch):d91871446d6baee8397522c4fa10d45985aa8645"meta-fsl-arm-extra =
"(nobranch):456c27085a70bb1385a4c2e28ba80ac74d6f533e"meta-fsl-demos=
"(nobranch):27fdb2f2642ecd55d5633bde880dd4c37acd0d42"NOTE: Preparing
runqueueNOTE: Tainting hash to force rebuild of task
/home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
, do_compileNOTE: Executing SetScene
TasksNOTE: Executing RunQueue TasksERROR: Function failed: do_compile (log
file is located at
/home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793)ERROR:
Logfile of failure stored in:
/home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793Log
data follows:| DEBUG: Executing shell function do_compile| NOTE: make -j 4
uImage CC=arm-poky-linux-gnueabi-gcc  -mno-thumb-interwork -marm
LD=arm-poky-linux-gnueabi-ld.bfd   LOADADDR=0x10008000|   HOSTCC
scripts/basic/fixdep|   HOSTCC  scripts/kconfig/conf.o|   HOSTCC
scripts/kconfig/zconf.tab.o|   HOSTLD  scripts/kconfig/conf|
scripts/kconfig/conf --silentoldconfig Kconfig| ***| *** Configuration file
".config" not found!| ***| *** Please run some configurator (e.g. "make
oldconfig" or| *** "make menuconfig" or "make xconfig").| ***| make[2]: ***
[silentoldconfig] Error 1| make[1]: *** [silentoldconfig] Error 2| make:
*** No rule to make target `include/config/auto.conf', needed by
`include/config/kernel.release'.  Stop.| ERROR: oe_runmake failed| WARNING:
exit code 1 from a shell command.| ERROR: Function failed: do_compile (log
file is located at
/home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793)ERROR:
Task 4
(/home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
, do_compile) failed with exit code '1'NOTE:
Tasks Summary: Attempted 247 tasks of which 246 didn't need to be rerun and
1 failed.Summary: 1 task failed:
/home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb
, do_compileSummary: There was 1 ERROR message
shown, returning a non-zero exit code.*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] [RFT] Moving on from eglibc to glibc 2.20

[Khem Raj]

Hi All

As we all know eglibc has been merged back into glibc and 2.19 was the
last release, here I have put together the recipes for upcoming glibc
2.20 release and removed eglibc 2.19 in favor of move.

I also thought about leaving eglibc in there but then eglibc and glibc
were pretty much same as they always have been that it would be an
incremental change with lot more patches this time.

The tree is here

http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-to-glibc-2.20

This has not recieved much testing yet and I am looking out for helping
hands here, so try it out in your buid environments and machines of
interest and report back on issues.

The patches also forward port the options group support and few other
patches from eglibc, details are in commit logs, which I think would make 
good candidates for future glibc merge.

This tree will be reworked and rebased so sync back if you see issues
which we will address here

Thanks for your help

-Khem
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto