From: Troy Benjegerdes <troy.benjegerdes@sifive.com>
To: Anup Patel <anup@brainfault.org>
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
"palmer@sifive.com" <palmer@sifive.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
"jamez@wit.com" <jamez@wit.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"schwab@suse.de" <schwab@suse.de>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"aou@eecs.berkeley.edu" <aou@eecs.berkeley.edu>,
"sachin.ghadi@sifive.com" <sachin.ghadi@sifive.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ynezz@true.cz" <ynezz@true.cz>,
"yash.shah@sifive.com" <yash.shah@sifive.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
Atish Patra <atish.patra@wdc.com>, Bin Meng <bmeng.cn@gmail.com>,
Lukas Auer <lukas.auer@aisec.fraunhofer.de>
Subject: Re: [PATCH v2 0/2] Add macb support for SiFive FU540-C000
Date: Tue, 18 Jun 2019 11:49:51 -0500 [thread overview]
Message-ID: <946B2B53-7A16-4B8D-8CB9-34EFFB9E84D6@sifive.com> (raw)
In-Reply-To: <CAAhSdy3zODw=JFaN=2F4K5-umihJDivLO8J8LBdkFkuZgzu41Q@mail.gmail.com>
> On Jun 18, 2019, at 4:32 AM, Anup Patel <anup@brainfault.org> wrote:
>
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=72296bde4f4207566872ee355950a59cbc29f852
I added your patches, along with two of mine, and rebased them
to the latest U-boot master, and put them on the ‘to-upstream’ branch
at https://github.com/sifive/u-boot/tree/to-upstream
I am most interested in review of the patch that adds the DTS files
from Linux to U-boot, along with a ‘-u-boot.dtsi’ file which includes
several extra things, most notably an ethernet entry [1] which does
not match the new proposed changes for the MacB driver that Yash
is working on.
How close are we to consensus on the new “sifive,fu540-macb”
device tree entry format? Is this something that is stable enough to
start basing some work in M-mode U-boot on yet, or do we expect
more changes?
[1] https://github.com/sifive/u-boot/commit/35e4168e36139722f30143a0ca0aa8637dd3ee04#diff-27d2d375ddac52f1bca71594075e1be4R93
next prev parent reply other threads:[~2019-06-18 16:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 4:19 [PATCH v2 0/2] Add macb support for SiFive FU540-C000 Yash Shah
2019-06-17 4:19 ` [PATCH v2 1/2] macb: bindings doc: add sifive fu540-c000 binding Yash Shah
2019-06-17 8:56 ` Paul Walmsley
2019-06-17 4:19 ` [PATCH v2 2/2] macb: Add support for SiFive FU540-C000 Yash Shah
2019-06-17 15:58 ` Andrew Lunn
2019-06-18 4:04 ` Yash Shah
2019-06-17 4:43 ` [PATCH v2 0/2] Add macb " Yash Shah
2019-06-17 8:25 ` Andreas Schwab
2019-06-17 9:58 ` Paul Walmsley
2019-06-17 10:01 ` Andreas Schwab
2019-06-17 10:05 ` Paul Walmsley
2019-06-17 10:14 ` Andreas Schwab
2019-06-17 11:34 ` Paul Walmsley
2019-06-17 14:14 ` Troy Benjegerdes
2019-06-17 14:20 ` Paul Walmsley
2019-06-17 18:42 ` Alistair Francis
2019-06-18 3:26 ` Paul Walmsley
2019-06-18 9:32 ` Anup Patel
2019-06-18 16:49 ` Troy Benjegerdes [this message]
2019-06-18 23:40 ` Atish Patra
2019-06-18 23:11 ` Alistair Francis
2019-06-17 10:22 ` Yash Shah
2019-06-17 10:28 ` Paul Walmsley
2019-06-17 11:15 ` Yash Shah
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=946B2B53-7A16-4B8D-8CB9-34EFFB9E84D6@sifive.com \
--to=troy.benjegerdes@sifive.com \
--cc=Alistair.Francis@wdc.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atish.patra@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=jamez@wit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lukas.auer@aisec.fraunhofer.de \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=sachin.ghadi@sifive.com \
--cc=schwab@suse.de \
--cc=yash.shah@sifive.com \
--cc=ynezz@true.cz \
/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;
as well as URLs for NNTP newsgroup(s).