All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Singh, Vishnu" <v-singh1@ti.com>
To: "Hegde, Yogesh" <y-hegde@ti.com>
Cc: "meta-arago@lists.yoctoproject.org"
	<meta-arago@lists.yoctoproject.org>,
	"Eatmon, Ryan" <reatmon@ti.com>,
	"denis@denix.org" <denis@denix.org>
Subject: Re: [meta-arago] [master][RFC PATCH] packagegroup-arago-tisdk-connectivity: Enable zeroconf ip support
Date: Thu, 22 Jan 2026 07:02:27 +0000	[thread overview]
Message-ID: <7fb12e2ff5b64281a5e27cab636dd4d3@ti.com> (raw)
In-Reply-To: <20260122064911.njy4xh57r356ag2g@yogi-work-pc>

Will be sending new patch, as the new zeroconf-autoip service is not required.

-----Original Message-----
From: Hegde, Yogesh <y-hegde@ti.com> 
Sent: Thursday, January 22, 2026 12:19 PM
To: Singh, Vishnu <v-singh1@ti.com>
Cc: meta-arago@lists.yoctoproject.org; Eatmon, Ryan <reatmon@ti.com>; denis@denix.org
Subject: Re: [meta-arago] [master][RFC PATCH] packagegroup-arago-tisdk-connectivity: Enable zeroconf ip support

On 16:33-20260119, vishnu singh via lists.yoctoproject.org wrote:
> From: Vishnu Singh <v-singh1@ti.com>
> 
> Dante DEP useage zeroconf for Dante network IP addresses.
> Zeroconf provide the IP network without manual configuation, and 
> avahi-autoipd is for auto ip assignment.
> To get the zeroconf ip at bootup, zeroconf-autoip service is used.
There are few typos in description. useage -> usage and configuation -> configuration. 
> 
> Signed-off-by: Vishnu Singh <v-singh1@ti.com>
> ---
>  .../zeroconf-autoip/zeroconf-autoip.bb        | 30 +++++++++++++++++++
>  .../zeroconf-autoip/zeroconf-autoip/README    |  1 +
>  .../zeroconf-autoip/zeroconf-autoip@.service  | 12 ++++++++  
> .../packagegroup-arago-tisdk-connectivity.bb  |  7 +++++
>  4 files changed, 50 insertions(+)
>  create mode 100644 
> meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-autoip
> .bb  create mode 100644 
> meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-autoip
> /README  create mode 100644 
> meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-autoip
> /zeroconf-autoip@.service
> 
> diff --git 
> a/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip.bb 
> b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip.bb
> new file mode 100644
> index 00000000..4b59a7e6
> --- /dev/null
> +++ b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-
> +++ autoip.bb
> @@ -0,0 +1,30 @@
> +SUMMARY = "Zerconf autoip"
Typo Zerconf -> Zeroconf.
> +DESCRIPTION = "Zeroconf IP assignment using avahi autoipd"
> +LICENSE = "MIT"
README file contains TI-TFL, It is a bit confusing due to 2 different licenses mentioned. Can you clarify the correct license and include the correct license text in the README. 
> +LIC_FILES_CHKSUM = "file://README;md5=102e8ceedf1b96837ba2eefc0d47f4e6"
> +
> +FILESEXTRAPATHS:prepend := "${THISDIR}/${PN}:"
> +
> +COMPATIBLE_MACHINE = "am62dxx"
> +
> +SRC_URI = "file://zeroconf-autoip@.service \
> +	file://README \
> +"
> +
> +S = "${UNPACKDIR}"
> +
> +inherit systemd
> +
> +SYSTEMD_SERVICE:${PN} = "zeroconf-autoip@eth0.service zeroconf-autoip@eth1.service"
> +SYSTEMD_AUTO_ENABLE = "enable"
> +
> +do_install() {
> +	install -d ${D}${systemd_system_unitdir}
> +	install -m 0644 ${WORKDIR}/zeroconf-autoip@.service 
> +${D}${systemd_system_unitdir}/ }
> +
> +FILES:${PN}= " \
> +	${systemd_system_unitdir} \
> +	${systemd_system_unitdir}/zeroconf-autoip@.service \ "
systemd bbclass automatically handles service files, I think it is safe to drop the FILES variable completely. 
> +PR = "r0"
> diff --git 
> a/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip/README 
> b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip/README
> new file mode 100644
> index 00000000..1ad1d419
> --- /dev/null
> +++ b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-
> +++ autoip/README
> @@ -0,0 +1 @@
> +TI-TFL
> diff --git 
> a/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip/zeroconf-autoip@.service 
> b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-auto
> ip/zeroconf-autoip@.service
> new file mode 100644
> index 00000000..952a8c60
> --- /dev/null
> +++ b/meta-arago-distro/recipes-connectivity/zeroconf-autoip/zeroconf-
> +++ autoip/zeroconf-autoip@.service
> @@ -0,0 +1,12 @@
> +[Unit]
> +Description=zerocnf-autoipd for %i interface After=network.target
> +
> +[Service]
> +ExecStart=/usr/sbin/avahi-autoipd --force-bind %i 
> +ExecStop=/usr/sbin/avahi-autoipd -k %i Restart=on-failure
> +RestartSec=30
> +
> +[Install]
> +WantedBy=multi-user.target
> diff --git 
> a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisd
> k-connectivity.bb 
> b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisd
> k-connectivity.bb
> index 0a8d4493..66aa4872 100644
> --- 
> a/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-tisd
> k-connectivity.bb
> +++ b/meta-arago-distro/recipes-core/packagegroups/packagegroup-arago-
> +++ tisdk-connectivity.bb
> @@ -53,6 +53,11 @@ BT_TI = "\
>      bt-enable \
>      bt-fw \
>  "
> +ZEROCONF_TI = "\
> +	zeroconf \
> +	avahi-autoipd \
Since services in zeroconf-autoip uses avahi-autoipd, best to include avahi-autoipd as RDEPENDS in zeroconf-autoip recipe.
> +	zeroconf-autoip \
> +"
>  
>  CONNECTIVITY_RDEPENDS = " \
>      htop \
> @@ -68,6 +73,8 @@ CONNECTIVITY_RDEPENDS = " \  
> CONNECTIVITY_RDEPENDS:append:ti33x = " ${BT_TI}"
>  CONNECTIVITY_RDEPENDS:append:ti43x = " ${BT_TI}"
>  CONNECTIVITY_RDEPENDS:append:am57xx = " ${BT_TI}"
> +CONNECTIVITY_RDEPENDS:append:am62dxx = " ${ZEROCONF_TI}"
> +
>  
>  RDEPENDS:${PN} = "\
>      ${CONNECTIVITY_RDEPENDS} \
> --
> 2.50.1
> 
> 
> 
> 

Thanks
Yogesh 


      reply	other threads:[~2026-01-22 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-19 11:03 [master][RFC PATCH] packagegroup-arago-tisdk-connectivity: Enable zeroconf ip support vishnu singh
2026-01-22  6:49 ` [meta-arago] " Yogesh Hegde
2026-01-22  7:02   ` Singh, Vishnu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fb12e2ff5b64281a5e27cab636dd4d3@ti.com \
    --to=v-singh1@ti.com \
    --cc=denis@denix.org \
    --cc=meta-arago@lists.yoctoproject.org \
    --cc=reatmon@ti.com \
    --cc=y-hegde@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.