From: Frank Terbeck <ft@bewatermyfriend.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: help-guix@gnu.org
Subject: Re: Kernel module build error with system image cross-build
Date: Fri, 26 Aug 2022 01:08:20 +0200 [thread overview]
Message-ID: <87sfljncpn.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <87k06whfxt.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Thu, 25 Aug 2022 10:42:54 +0200")
pelzflorian@pelzflorian.de wrote:
> Hello Frank, sorry for the late reply.
Hey Florian, no worries! I'm only working on this when time permits
anyway. It is cool when things aren't complete monologues, though. So
thanks for chiming in. :)
It's interesting to see how Guix does these things.
> HDMI stays black, but I can’t
> find the cables for my UART adapter, so I cannot properly test. I think
Ah, so you tried, nice! I couldn't yet… Maybe this weekend.
> you are doing it right, but if what used to work does not, perhaps an
> easier way would be to copy the rock64.scm image, and adapt that to use
> the Beaglebone Black’s u-boot and the kernel linux-libre-arm-generic
> instead of linux-libre-arm64-generic, then pass this file to guix system
> image.
Certainly. I didn't even know gnu/system/images was a place to look. :)
I'm still finding out about Guix's structure and API. Apart from a
couple of package definitions, I didn't do a lot yet. Things in this
field do feel a little all over to place, though. There's these tem-
plates, then there's gnu/system/install.scm (which also has a rock64-
installation-os definition) and also this images place. Maybe there's a
point to it, that I'm not seeing. Or maybe it's just a lack of manpower
to keep stuff up to date when the rest of the project moves along at a
swift pace.
> But perhaps this still is the wrong kernel and you need an older
> kernel, either as an old linux-libre-arm-generic-4.19 kernel or an old
> kernel via a Guix inferior.
I think the interface into the kernel data is lacking. It might be use-
ful to have an interface to the kernel's ‘.config’, as well as meta data
files such at the mentioned ‘modules.builtin’.
The fact that the beaglebone specs reference "omap_hsmmc" is correct on
its face, because that driver is indeed required. If it's builtin, then
not finding the file is to be expected and not an issue.
With better introspection to the kernel's build configuration, an OS
specification could easier react to upstream changes, I think.
Not sure if that sort of discussion isn't more appropriate for -devel.
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2022-08-25 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 0:59 Kernel module build error with system image cross-build Frank Terbeck
2022-08-23 16:57 ` Frank Terbeck
2022-08-25 8:42 ` pelzflorian (Florian Pelz)
2022-08-25 23:08 ` Frank Terbeck [this message]
2022-08-26 14:50 ` pelzflorian (Florian Pelz)
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=87sfljncpn.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).