unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: me@tobias.gr, w@wmeyer.eu, 71372@debbugs.gnu.org, leo@famulari.name
Subject: [bug#71372] [PATCH] gnu: linux-libre: Add 6.9-riscv.conf
Date: Thu, 13 Jun 2024 11:54:05 +0000	[thread overview]
Message-ID: <87tthx9hya.fsf@kitej> (raw)
In-Reply-To: <87o78euz9z.fsf@iscas.ac.cn> (Zheng Junjie's message of "Thu, 06 Jun 2024 18:43:52 +0800")

[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]

Zheng Junjie <zhengjunjie@iscas.ac.cn> skribis:

> Guillaume Le Vaillant <glv@posteo.net> writes:
>
>> Zheng Junjie <zhengjunjie@iscas.ac.cn> skribis:
>>
>>> Guillaume Le Vaillant <glv@posteo.net> writes:
>>>
>>>> Zheng Junjie <zhengjunjie@iscas.ac.cn> skribis:
>>>>
>>>>> * gnu/packages/aux-files/linux-libre/6.9-riscv.conf: New file.
>>>>> * Makefile.am (AUX_FILES): Register it.
>>>>>
>>>>> [...]
>>>>> +#
>>>>> +# NVME Support
>>>>> +#
>>>>> +CONFIG_NVME_KEYRING=y
>>>>> +CONFIG_NVME_CORE=y
>>>>> +# CONFIG_BLK_DEV_NVME is not set
>>>>> [...]
>>>>
>>>> Hi.
>>>> If CONFIG_BLK_DEV_NVME is not set, wouldn't that prevent the kernel from
>>>> seeing the NVME drive (as /dev/nvme* will not appear)?
>>>> Or is it disabled on purpose because it doesn't work well yet?
>>>
>>> I'm not familiar with kernel options, so just i no set them, But in
>>> Visionfive 2 when I enabled it, I couldn't see /dev/nvme* either.
>>
>> Ok. Maybe some other options will be necessary to activate NVME drive
>> support. But we can try that later, and not delay merging this patch
>> adding the missing RISC-V kernel configuration.
> thanks, i push.
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=4ae4311b31f1687714a01196a20bdc8b5c2a5843
>
> Keep open to discuss missing riscv kernel configuration.

According to the table in [1], PCIe support for the JH7110 processor of
the VisionFive 2 board will be in the regular Linux kernel starting at
version 6.11. As we're currently using version 6.9, this is why the NVME
drive is not detected even with the CONFIG_BLK_DEV_NVME option
activated.

[1] https://rvspace.org/en/project/JH7110_Upstream_Plan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

  parent reply	other threads:[~2024-06-13 11:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05  6:16 [bug#71372] [PATCH] gnu: linux-libre: Add 6.9-riscv.conf Zheng Junjie
2024-06-05  7:34 ` Guillaume Le Vaillant
2024-06-06  5:45   ` Zheng Junjie
2024-06-06  8:58     ` Guillaume Le Vaillant
2024-06-06 10:43       ` Zheng Junjie
2024-06-06 17:26         ` Wilko Meyer
2024-06-17 16:26           ` Zheng Junjie
2024-06-13 11:54         ` Guillaume Le Vaillant [this message]
2024-06-17 16:29           ` bug#71372: " Zheng Junjie

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=87tthx9hya.fsf@kitej \
    --to=glv@posteo.net \
    --cc=71372@debbugs.gnu.org \
    --cc=leo@famulari.name \
    --cc=me@tobias.gr \
    --cc=w@wmeyer.eu \
    --cc=zhengjunjie@iscas.ac.cn \
    /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).