public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "André Erdmann" <dywi@mailerd.de>
To: gentoo-soc <gentoo-soc@lists.gentoo.org>
Cc: Rafael Martins <rafaelmartins@gentoo.org>
Subject: [gentoo-soc] kernelconfig - progress report #10
Date: Mon, 1 Aug 2016 02:55:50 +0200	[thread overview]
Message-ID: <CAGrucu1sVOpw2GmQNOkMEiRe=1DDYoRn-UzoGQQOyLmdZFUD-Q@mail.gmail.com> (raw)

Hi everyone,


== Brief summary of this project ==

kernelconfig is about generating kernel configuration files,
using various sources such as curated defconfigs, detected hardware,
installed packages and user input.

The project's code can be found at [0].


== This week's progress ==

This week's work has been about extending hardware detection.

Creation of files necessary for "modalias"-based hardware detection has
been added. Basically, "make allmodconfig && make modules" is run to create
all modules, and the desired "modules.alias" file is then created with depmod.
Since this takes a lot of time to compile, it is not done automatically.
Instead, kernelconfig offers a command for creating "modalias" files,
and tries to use previously created files (depending on e.g. kernel version).

A "hardware collector" shell script has been written,
which allows to detect required/useful kernel modules on another machine
than the one configuring/building the kernel.
The idea here is to run this script on a live system (practically
anything with a few busybox applets), and feed kernelconfig with the data.


== Plans for the next week ==

* write documentation for "hardware detection"

* start with "pm integration",
  so far there is a draft-doc [1] on what could be done


[0] https://github.com/dywisor/kernelconfig
[1] https://github.com/dywisor/kernelconfig/blob/2f4ceefc79d2ca677e63537ade42d6bff10d0e00/doc/rst/draft/pmintegration.rst

Regards,
André E.


                 reply	other threads:[~2016-08-01  0:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='CAGrucu1sVOpw2GmQNOkMEiRe=1DDYoRn-UzoGQQOyLmdZFUD-Q@mail.gmail.com' \
    --to=dywi@mailerd.de \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=rafaelmartins@gentoo.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