From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Packaging CDEmu and VHBA kernel module
Date: Tue, 05 Mar 2019 18:35:17 +0100 [thread overview]
Message-ID: <87tvghfcmi.fsf@ambrevar.xyz> (raw)
In-Reply-To: <87k1i27j5m.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 903 bytes --]
Hi again,
Thanks for the tips, Chris, and sorry for the long silence.
> https://lists.gnu.org/archive/html/guix-devel/2016-07/msg01457.html
> https://lists.gnu.org/archive/html/guix-devel/2018-02/msg00446.html
> https://lists.gnu.org/archive/html/guix-devel/2017-12/msg00221.html
Hmmm... As far as I get it, none of those links tackle the issue of building an
_external_ kernel module. The modules mentioned in the links are all part of
the linux-libre kernel.
Currently it seems that we have no way to build an external module. It's quite problematic.
I've sent a patch: 34758@debbugs.gnu.org.
It needs the following:
- Fix vhba-module 'build phase.
- Optional: make a udev-related service to simplify the setup. The service
won't work if the module is not included in the kernel.
I'll continue the discussion there.
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2019-03-05 17:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 22:48 Packaging CDEmu and VHBA kernel module Pierre Neidhardt
2019-02-14 10:34 ` Chris Marusich
2019-03-05 17:35 ` Pierre Neidhardt [this message]
2019-04-14 17:13 ` Pierre Neidhardt
2019-04-14 17:23 ` Danny Milosavljevic
2019-04-14 17:24 ` Pierre Neidhardt
2019-04-14 17:28 ` Pierre Neidhardt
2019-04-14 17:31 ` Danny Milosavljevic
2019-04-14 17:57 ` Tobias Geerinckx-Rice
2019-04-14 17:39 ` Tobias Geerinckx-Rice
2019-06-23 3:06 ` Chris Marusich
2019-06-23 6:39 ` Pierre Neidhardt
2019-06-23 6:40 ` Pierre Neidhardt
2019-06-24 13:04 ` Danny Milosavljevic
2019-06-23 22:03 ` Chris Marusich
2019-06-24 7:52 ` Pierre Neidhardt
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=87tvghfcmi.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=cmmarusich@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.