mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alistair Francis <Alistair.Francis@wdc.com>
To: "paul.walmsley@sifive.com" <paul.walmsley@sifive.com>
Cc: "palmer@sifive.com" <palmer@sifive.com>,
	"linux-riscv@lists.infradead.org"
	<linux-riscv@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] RISC-V: defconfig: Enable Generic PCIE by default
Date: Fri, 21 Dec 2018 23:03:21 +0000	[thread overview]
Message-ID: <ac8f991f5c3e0b5de8dea6b187e1daca198b4677.camel@wdc.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1812211433290.777@viisi.sifive.com>

On Fri, 2018-12-21 at 14:34 -0800, Paul Walmsley wrote:
> 
> On Fri, 21 Dec 2018, Alistair Francis wrote:
> 
> > On Fri, 2018-12-21 at 11:27 -0800, Paul Walmsley wrote:
> > > On Fri, 21 Dec 2018, Alistair Francis wrote:
> > > 
> > > > When the MicroSemi driver does eventually go upstream this will
> > > > probably have to be discussed though as either the config or
> > > > device
> > > > tree will need to be edited to ensure only one PCIe device is
> > > > present.
> > > 
> > > The right way to do that is to have two separate DT files: one
> > > for the 
> > > HiFive-U board alone; the other for the HiFive-U plus the
> > > expansion 
> > > board combo.  There shouldn't be any problems with keeping both 
> > > drivers enabled in the defconfig.
> > 
> > Agreed, the only problem is that the device tree comes from the
> > boards
> > firmware at the moment.
> 
> The switchover is in progress:
> 
> https://lore.kernel.org/linux-riscv/41dac7a1-3f66-6a3f-8a68-206688e5bd9e@sifive.com/T/#t

Great! I didn't know it was in progress.

Alistair

> 
> 
> - Paul
> 

  reply	other threads:[~2018-12-21 23:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 19:06 Alistair Francis
2018-12-21 19:13 ` Paul Walmsley
2018-12-21 19:22   ` Alistair Francis
2018-12-21 19:27     ` Paul Walmsley
2018-12-21 22:11       ` Alistair Francis
2018-12-21 22:34         ` Paul Walmsley
2018-12-21 23:03           ` Alistair Francis [this message]
2018-12-26 16:52       ` Palmer Dabbelt

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=ac8f991f5c3e0b5de8dea6b187e1daca198b4677.camel@wdc.com \
    --to=alistair.francis@wdc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@sifive.com \
    --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

all inboxes | Powered by JetHome®