[yocto] [dbus] [meta-raspberrypi] using dbus with system verilog

[Sherif Omran]

yes, see below, but my problem is with the systemVinit

DISTRO_FEATURES_append += " bluez5 bluez-utils bluetooth wifi alsa"
IMAGE_INSTALL_append += " linux-firmware-bcm43430 bluez5 bridge-utils
wpa-supplicant python-smbus i2c-tools"
DISTRO_FEATURES_append += " ext2 pulseaudio pam usbhost sbc alsa-plugins
${DISTRO_FEATURES_LIBC} "
PACKAGECONFIG_bluez += " --disable-systemd "
IMAGE_INSTALL_append += " bluez5-testtools bluez5-noinst-tools
libasound-module-bluez packagegroup-base-bluetooth "


IMAGE_INSTALL_append= " bluez5 pulseaudio-server libpulsecore sbc
pulseaudio-module-bluetooth-discover pulseaudio-module-bluez5-device
pulseaudio-module-bluez5-discover pulseaudio-$
DISTRO_FEATURES_remove = " x11 "
IMAGE_INSTALL_append= " screen "

On Mon, May 7, 2018 at 12:18 AM, Khem Raj <raj.khem at gmail.com> wrote:

>
> On Sun, May 6, 2018 at 2:02 AM Sherif Omran <sherifomran2000 at gmail.com>
> wrote:
>
>> hi
>> i created an os for raspberry pi 0 w, it uses system v, but dbus does not
>> start automatically and when i started it using a startup script and
>> exported its parameters, i still get the following when i start pulseaudio
>> -vvvv.
>>
>> Unknown interface org.freedesktop.DBUS.Introspectable
>>
>> Unknown interface org.bluez.AgentManager1 found
>>
>> Unknown interface org.bluez.ProfileManager1
>>
>> Unknown interface org.freedesktop.DBUS.Properties found
>>
>> Unknown interace org.bluez.Media1 found
>>
>> Unknown interface org.bluez.NetworkServer1 found
>>
>>
> Have you included bluez in image ?
>
>
>>
>> What is the best way to start dbus? should i edit in kernel configuration?
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto at yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20180507/9bd7d2d5/attachment.html>