unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0@n0.is
To: guix-devel@gnu.org
Subject: Re: GSoC
Date: Tue, 06 Feb 2018 10:33:56 +0000	[thread overview]
Message-ID: <87k1vqv23v.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87bmh3kbd9.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 05 Feb 2018 10:57:06 +0100")

On second thoughts I think it's okay to have all of this in
public, there are no stupid questions.

On Mon, 05 Feb 2018, ludo@gnu.org (Ludovic Courtès) wrote:
> Heya,
>
> ng0@n0.is skribis:
>
>> Sorry for the offlist message, but I thought since you list
>> yourself as possible mentor for the item I'd ask.
>
> What?  I didn’t add myself there I think, we should find out where that
> comes from.  :-)

So.. who added Ludovic to the RISC-V item? And if not Ludovic,
who'd be a good mentor for this item (and has time to spend on
it)? Manolis has worked on porting to a different kernel, Efraim
has worked on porting to another architecture.

>> With regards to RISC-V porting: a question I don't dare asking in
>> public because it's answer could be too obvious: is the porting
>> possible without owning any real RISC-V hardware?
>
> I know very little about RISC-V, but I suppose QEMU could help (and most
> of the porting work is about getting cross-compilation right.)
>
>> I think at this point I know enough in Guix to port it to another
>> architecture and would apply for this when the GSoC student
>> applications are open, depending on your reply.
>
> Cool.  I think you’re welcome to discuss publicly the details and, as a
> last resort, privately with the person who submitted this idea (I don’t
> remember who that was, but we could ask on the list.)
>
> Cheers,
> Ludo’.
>

So, ahead of time, I'm interested in porting Guix to
RISC-V. Looking at the timeline on the Google GSoC website it
falls into my next semester where I can't tell you right how many
hours I have available.
Students applications period starts in March, so that gives me
enough time to look into how porting without owning the hardware
works, refreshing my memory on it (recently I've read about slow
but native compiling of ARM on qemu).
As Ludovic wrote, and by my understanding of porting, it will
mostly cover bootstrap + ideally having a compiled (better:
functional) Guix on RISC-V?
-- 
ng0 :: https://ea.n0.is
A88C8ADD129828D7EAC02E52E22F9BBFEE348588 :: https://ea.n0.is/keys/

       reply	other threads:[~2018-02-06 10:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87bmh4qrf5.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me>
     [not found] ` <87bmh3kbd9.fsf@gnu.org>
2018-02-06 10:33   ` ng0 [this message]
2018-02-08 11:25     ` GSoC ng0
2018-02-08 12:09       ` GSoC Gábor Boskovits
2018-02-08 12:31         ` GSoC ng0
2018-02-08 12:41           ` GSoC ng0
2018-02-08 13:57     ` RISC-V port for GSoC? Ludovic Courtès
2018-02-08 14:42       ` ng0
2018-02-08 18:42       ` Ricardo Wurmus
2018-02-08 19:19         ` Gábor Boskovits
2018-02-08 19:34         ` ng0
2018-02-08 22:25           ` Ludovic Courtès
2018-02-08 16:42     ` ARM compilation via qemu binfmt - Assertion failure Danny Milosavljevic
2018-02-10 23:45       ` Chris Marusich
2018-02-11  1:07         ` bug#30394: " Leo Famulari
2018-02-11  9:53         ` Pjotr Prins
2018-02-16 10:35       ` bug#30394: " Ludovic Courtès
2014-02-19 19:38 GSoC Andreas Enge
2014-02-19 21:57 ` GSoC Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k1vqv23v.fsf@abyayala.i-did-not-set--mail-host-address--so-tickle-me \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).