All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Potin Lai <potin.lai.pt@gmail.com>
Cc: Enguerrand de Ribaucourt
	<enguerrand.de-ribaucourt@savoirfairelinux.com>,
	openembedded-devel <openembedded-devel@lists.openembedded.org>,
	joe <joe@deserted.net>, Patrick Williams <patrick@stwcx.xyz>
Subject: Re: [meta-networking][PATCH V2] mdio-tools: add recipes
Date: Mon, 16 May 2022 22:36:30 -0700	[thread overview]
Message-ID: <CAMKF1soaoAh9Dm_QD_a80YXHEyb=h=Zr9Jid7Ks9pEtbEbcqAg@mail.gmail.com> (raw)
In-Reply-To: <08c924ec-b924-03fd-9138-cd04083a0c6a@gmail.com>

perhaps get this enabled by default in linux-yocto kernel defconfigs

On Mon, May 16, 2022 at 9:44 PM Potin Lai <potin.lai.pt@gmail.com> wrote:
>
>
> Enguerrand de Ribaucourt 於 2022/2/2 下午 05:59 寫道:
> > Thank you for your feedback. The build fails on those MACHINEs because the kernel
> > configuration does not enables the MDIO bus support.
> > I could successfully build the recipes on both MACHINEs by adding the following
> > kernel configuration fragment:
> >
> > ---
> > CONFIG_MDIO_DEVICE=y
> > CONFIG_MDIO_BUS=y
> > # CONFIG_MDIO_BITBANG is not set
> > # CONFIG_MDIO_BCM_UNIMAC is not set
> > # CONFIG_MDIO_MVUSB is not set
> > # CONFIG_MDIO_MSCC_MIIM is not set
> > # CONFIG_MDIO_THUNDER is not set
> >
> > #
> > # MDIO Multiplexers
> > #
> > # CONFIG_PCS_XPCS is not set
> > ---
> >
> > What would be the best way to approach this?
> >
> > ----- Original Message -----
> >> From: "raj khem" <raj.khem@gmail.com>
> >> To: "Enguerrand de Ribaucourt" <enguerrand.de-ribaucourt@savoirfairelinux.com>
> >> Cc: "openembedded-devel" <openembedded-devel@lists.openembedded.org>, "joe" <joe@deserted.net>
> >> Sent: Wednesday, February 2, 2022 6:35:22 AM
> >> Subject: Re: [meta-networking][PATCH V2] mdio-tools: add recipes
> >> this fails on mips
> >> https://errors.yoctoproject.org/Errors/Details/623861/
> >> aarch64
> >> https://errors.yoctoproject.org/Errors/Details/623865/
> >> On Tue, Feb 1, 2022 at 6:45 AM Enguerrand de Ribaucourt
> >> <enguerrand.de-ribaucourt@savoirfairelinux.com> wrote:
> >>> ----- Mail original -----
> >>>> De: "Enguerrand de Ribaucourt" <enguerrand.de-ribaucourt@savoirfairelinux.com>
> >>>> À: openembedded-devel@lists.openembedded.org
> >>>> Cc: "raj khem" <raj.khem@gmail.com>, joe@deserted.net, "Enguerrand de
> >>>> Ribaucourt"
> >>>> <enguerrand.de-ribaucourt@savoirfairelinux.com>
> >>>> Envoyé: Mardi 1 Février 2022 15:26:10
> >>>> Objet: [meta-networking][PATCH V2] mdio-tools: add recipes
> >>> Hi,
> >>> mdio-tools is a similar tool to phytool, by the same author, which is already
> >>> present in meta-networking. This one allows a more low-level access to the MDIO
> >>> bus as well as writing with the use of a kernel module.
> >>> I re-submitted the patch with some small corrections to respect coding style
> >>> conventions:
> >>> 1. Moved in recipes-support
> >>> 2. Removed version in mdio-tools_1.0.1.inc filename
> >>> Please let me know if these recipes are relevant to meta-networking or if you
> >>> have any comments about them.
> >>> Thank you for your time.
> >>>> Self-description from the README: mdio-tools is a low-level debug tool
> >>>> for communicating with devices attached to an MDIO bus.
> >>>> Signed-off-by: Enguerrand de Ribaucourt
> >>>> <enguerrand.de-ribaucourt@savoirfairelinux.com>
> >>>> ---
> >>>> .../mdio-tools/mdio-netlink_1.0.1.bb | 13 +++++++++++++
> >>>> .../recipes-support/mdio-tools/mdio-tools.inc | 8 ++++++++
> >>>> .../recipes-support/mdio-tools/mdio-tools_1.0.1.bb | 9 +++++++++
> >>>> 3 files changed, 30 insertions(+)
> >>>> create mode 100644
> >>>> meta-networking/recipes-support/mdio-tools/mdio-netlink_1.0.1.bb
> >>>> create mode 100644 meta-networking/recipes-support/mdio-tools/mdio-tools.inc
> >>>> create mode 100644
> >>>> meta-networking/recipes-support/mdio-tools/mdio-tools_1.0.1.bb
> >>>> diff --git a/meta-networking/recipes-support/mdio-tools/mdio-netlink_1.0.1.bb
> >>>> b/meta-networking/recipes-support/mdio-tools/mdio-netlink_1.0.1.bb
> >>>> new file mode 100644
> >>>> index 000000000..b50d33f90
> >>>> --- /dev/null
> >>>> +++ b/meta-networking/recipes-support/mdio-tools/mdio-netlink_1.0.1.bb
> >>>> @@ -0,0 +1,13 @@
> >>>> +require mdio-tools.inc
> >>>> +
> >>>> +DEPENDS += "virtual/kernel libmnl"
> >>>> +# This module requires Linux 5.6 higher
> >>>> +
> >>>> +S = "${WORKDIR}/git/kernel"
> >>>> +
> >>>> +inherit module
> >>>> +
> >>>> +EXTRA_OEMAKE = "KDIR=${STAGING_KERNEL_DIR}"
> >>>> +MODULES_INSTALL_TARGET = "install"
> >>>> +
> >>>> +RPROVIDES:${PN} += "kernel-module-mdio-netlink"
> >>>> diff --git a/meta-networking/recipes-support/mdio-tools/mdio-tools.inc
> >>>> b/meta-networking/recipes-support/mdio-tools/mdio-tools.inc
> >>>> new file mode 100644
> >>>> index 000000000..bba8960d8
> >>>> --- /dev/null
> >>>> +++ b/meta-networking/recipes-support/mdio-tools/mdio-tools.inc
> >>>> @@ -0,0 +1,8 @@
> >>>> +DESCRIPTION = "A low-level debug tool for communicating with devices attached
> >>>> to an MDIO bus"
> >>>> +SECTION = "networking"
> >>>> +HOMEPAGE = "https://github.com/wkz/mdio-tools"
> >>>> +LICENSE = "GPLv2"
> >>>> +LIC_FILES_CHKSUM =
> >>>> "file://${WORKDIR}/git/COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
> >>>> +
> >>>> +SRC_URI = "git://github.com/wkz/mdio-tools.git;protocol=https;branch=master"
> >>>> +SRCREV = "b40809dd59aa199d8afc307e228b55eeae06b17e"
> >>>> diff --git a/meta-networking/recipes-support/mdio-tools/mdio-tools_1.0.1.bb
> >>>> b/meta-networking/recipes-support/mdio-tools/mdio-tools_1.0.1.bb
> >>>> new file mode 100644
> >>>> index 000000000..cd4df3da0
> >>>> --- /dev/null
> >>>> +++ b/meta-networking/recipes-support/mdio-tools/mdio-tools_1.0.1.bb
> >>>> @@ -0,0 +1,9 @@
> >>>> +require mdio-tools.inc
> >>>> +
> >>>> +DEPENDS += "libmnl"
> >>>> +
> >>>> +S = "${WORKDIR}/git"
> >>>> +
> >>>> +inherit pkgconfig autotools
> >>>> +
> >>>> +RDEPENDS:${PN} = "kernel-module-mdio-netlink"
> >>>> --
> >>>> 2.25.1
> >
> Hi Maintainer,
>
> I am looking forward to add mdio-tools package support into openembedded. I find this post, but it looks not been updated for few month.
> Just wondering that would you give some advice for adding extra kernel configurations? or it is possible adding configs into defconfig for `mips` and `aarch64`?
>
> BR,
>
> Potin
>
>


      parent reply	other threads:[~2022-05-17  5:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <94691>
2022-02-01 14:26 ` [meta-networking][PATCH V2] mdio-tools: add recipes Enguerrand de Ribaucourt
2022-02-01 14:45   ` Enguerrand de Ribaucourt
2022-02-02  5:35     ` Khem Raj
2022-02-02  9:59       ` Enguerrand de Ribaucourt
     [not found]         ` <08c924ec-b924-03fd-9138-cd04083a0c6a@gmail.com>
2022-05-17  5:36           ` Khem Raj [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='CAMKF1soaoAh9Dm_QD_a80YXHEyb=h=Zr9Jid7Ks9pEtbEbcqAg@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=enguerrand.de-ribaucourt@savoirfairelinux.com \
    --cc=joe@deserted.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=patrick@stwcx.xyz \
    --cc=potin.lai.pt@gmail.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.