All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dinh Nguyen <dinguyen@kernel.org>
To: Petko Manolov <petko.manolov@konsulko.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	arnemaximilian.richter@draeger.com,
	martynas.grybauskas@draeger.com
Subject: Re: [PATCH v11 3/3] arm: dts: altera: add Draeger M48 CPU Module
Date: Fri, 16 Oct 2026 09:25:23 -0500	[thread overview]
Message-ID: <34c65b1d-a389-447b-96f4-e2a15ee37f99@kernel.org> (raw)
In-Reply-To: <20261016123346.GC15187@carbon.k.g>



On 10/16/26 07:33, Petko Manolov wrote:
> On 26-10-16 06:08:53, Dinh Nguyen wrote:
>>
>> On 10/15/26 09:58, Petko Manolov wrote:
>>> M48 is a heterogeneous board made by Draeger that is based on two
>>> independent cpus, that are monitoring each other.  One of them is
>>> imx6, the other is Altera SoCFPGA Cyclone 5.  The latter is booting
>>> independently off qspi.
> 
> <snip>
> 
>>> +&gmac0 {
>>> +	status = "okay";
>>> +	phy-mode = "rgmii";
>>> +	phy-handle = <&ethphy>;
>>> +
>>> +	mdio0 {
>>> +		#address-cells = <1>;
>>> +		#size-cells = <0>;
>>
>> You also need this here:  compatible = "snps,dwmac-mdio"
> 
> Thanks a lot.  Is there a way to send patches to Sashiko without bombing the
> LKML and, respectively, all of you guys?
> 
Yes, you can run sashiko locally. The instructions are in the sashiko 
project.

Dinh

      reply	other threads:[~2026-10-16 14:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-15 14:58 [PATCH v11 0/3] arm: dts: altera: add Draeger M48 CPU board Petko Manolov
2026-10-15 14:58 ` [PATCH v11 1/3] dt-bindings: vendor-prefixes: add Draeger AG Petko Manolov
2026-10-15 14:58 ` [PATCH v11 2/3] dt-bindings: arm: altera: add Draeger M48 dual-cpu board Petko Manolov
2026-10-15 14:58 ` [PATCH v11 3/3] arm: dts: altera: add Draeger M48 CPU Module Petko Manolov
2026-10-15 15:09   ` sashiko-bot
2026-10-16 11:08   ` Dinh Nguyen
2026-10-16 12:33     ` Petko Manolov
2026-10-16 14:25       ` Dinh Nguyen [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=34c65b1d-a389-447b-96f4-e2a15ee37f99@kernel.org \
    --to=dinguyen@kernel.org \
    --cc=arnemaximilian.richter@draeger.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martynas.grybauskas@draeger.com \
    --cc=petko.manolov@konsulko.com \
    --cc=robh@kernel.org \
    /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.