Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: Working device tree for the HifiveU
Date: Mon, 17 Jun 2019 15:28:33 +0200	[thread overview]
Message-ID: <mvmzhmg49z2.fsf@suse.de> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906170625480.32654@viisi.sifive.com> (Paul Walmsley's message of "Mon, 17 Jun 2019 06:26:42 -0700 (PDT)")

On Jun 17 2019, Paul Walmsley <paul.walmsley@sifive.com> wrote:

> We can't add the Ethernet data yet, since it hasn't been approved by the 
> DT maintainers.  But of course you can always add it yourself to your own 
> kernel branch, along with the driver.

Which driver?

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2019-06-17 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-17 10:14 Working device tree for the HifiveU Andreas Schwab
2019-06-17 10:58 ` Paul Walmsley
2019-06-17 12:11   ` Andreas Schwab
2019-06-17 12:19   ` Andreas Schwab
2019-06-17 12:47     ` Paul Walmsley
2019-06-17 12:49       ` Andreas Schwab
2019-06-17 13:21         ` Troy Benjegerdes
2019-06-17 13:31           ` Paul Walmsley
2019-06-17 13:35             ` Troy Benjegerdes
2019-06-17 13:41               ` Paul Walmsley
2019-06-17 13:50                 ` Andreas Schwab
2019-06-17 13:26         ` Paul Walmsley
2019-06-17 13:28           ` Andreas Schwab [this message]
2019-06-17 13:34             ` Paul Walmsley

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=mvmzhmg49z2.fsf@suse.de \
    --to=schwab@suse.de \
    --cc=linux-riscv@lists.infradead.org \
    --cc=paul.walmsley@sifive.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox