Linux-RISC-V Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mick@ics.forth.gr (Nick Kossifidis)
To: linux-riscv@lists.infradead.org
Subject: Post-4.19 WIP Branch Cleanup, riscv-linux-4.18, and 4.20 plans
Date: Mon, 10 Sep 2018 16:52:24 +0300	[thread overview]
Message-ID: <eeea61edbe84de12b2ef09f62d75f975@mailhost.ics.forth.gr> (raw)
In-Reply-To: <20180910134147.GA25264@infradead.org>

???? 2018-09-10 16:41, Christoph Hellwig ??????:
> On Thu, Sep 06, 2018 at 02:45:00AM -0700, Palmer Dabbelt wrote:
>> > I think gpio & pwm are required as well. I couldn't get networking up
>> > without the GPIO driver.
>> 
>> That makes sense: IIRC the GPIO twiddles the pins that control the 
>> Ethernet phy.
>> 
>> > https://github.com/riscv/riscv-linux/commit/7b012f300afcff77c20a4d84519f4bd2b9b17bd0
>> >
>> > https://github.com/riscv/riscv-linux/commit/d6e84658098c6f37875a9e4b151706c6b541dc0b
>> 
>> Thanks.  I've grabbed both of these into WIP branches for now, they're 
>> at
>> least the self contained type so it should be viable to start cleaning 
>> them
>> up, pending time.
> 
> Btw, do we have volunteers for given drivers?  I think Paul is trying
> to handle the serial driver.  I'll try to spend some time on one or 
> two,
> and have a SiFive board now.  but I won't really have time to try it
> until the end of the month as I'm busy travelling and at conferences.
> 

Hello all,

I recently got my hands on a SiFive board as well, and I plan to form a 
team here at FORTH to start working on RISC-V kernel support etc. How 
can I help ? I started reading the code under /arch/riscv to get an idea 
but is there a todo list somewhere or a wiki page ? On which git tree / 
branch are you working on ?

Thanks a lot for your work
Nick

  reply	other threads:[~2018-09-10 13:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-20 21:04 Post-4.19 WIP Branch Cleanup, riscv-linux-4.18, and 4.20 plans Palmer Dabbelt
2018-08-20 22:10 ` Christoph Hellwig
2018-08-21  1:28   ` Atish Patra
2018-08-20 22:11 ` Atish Patra
2018-09-06  9:45   ` Palmer Dabbelt
2018-09-10 13:41     ` Christoph Hellwig
2018-09-10 13:52       ` Nick Kossifidis [this message]
2018-09-20  0:06         ` Palmer Dabbelt
2018-09-10 17:13       ` Atish Patra
2018-09-20  0:06       ` 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=eeea61edbe84de12b2ef09f62d75f975@mailhost.ics.forth.gr \
    --to=mick@ics.forth.gr \
    --cc=linux-riscv@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox