mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rik van Riel <riel@surriel.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Mark Gross <mgross@linux.intel.com>,
	Giacomo Catenazzi <cate@debian.org>,
	Sam Ravnborg <sam@ravnborg.org>,
	linux-kernel@vger.kernel.org
Subject: Re: WANTED: kernel projects for CS students
Date: Tue, 16 Oct 2007 16:23:10 -0400	[thread overview]
Message-ID: <20071016162310.1891914f@bree.surriel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710162207540.4548@fbirervta.pbzchgretzou.qr>

On Tue, 16 Oct 2007 22:09:04 +0200 (CEST)
Jan Engelhardt <jengelh@computergmbh.de> wrote:
> On Oct 16 2007 13:06, Mark Gross wrote:
> >
> >base function:
> >Starting from a stock distro (FC, Ubuntu, OpenSuSE...) and put down a
> >kernel.org tree and automatically create a .config with all the
> >drivers needed for the platform I'm building on.
> 
> Too easy. Since opensuse's udev loads most of the modules for your
> hardware, all that would be needed is to transform the lsmod list of
> modules plus the static options in /proc/config.gz (stuff like
> psmouse) back into kconfig options ;-)

Well, at that point it does not know whether or not you
occasionally plug in an ipod or a digital camera.

Going back from the lsmod output to all the right CONFIG
options is also not as trivial as it sounds, due to all
the dependencies there are.

This project sounds like it could be a great undergraduate
project, maybe built on top of Ketchup to automatically
fetch, configure, compile and install a working kernel :)

Are there any volunteers to write down the project
description on the kernelnewbies.org wiki?

-- 
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan

  reply	other threads:[~2007-10-16 20:23 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-14 23:01 Rik van Riel
2007-10-15 10:40 ` WANG Cong
2007-10-15 17:13   ` Rik van Riel
2007-10-15 14:23 ` Sam Ravnborg
2007-10-15 15:10   ` Rik van Riel
2007-10-15 18:31     ` Sam Ravnborg
2007-10-15 16:31   ` Philippe Elie
2007-10-15 16:36     ` Philippe Elie
2007-10-15 16:52       ` Jan Engelhardt
2007-10-15 16:53       ` Xavier Bestel
2007-10-15 18:19     ` Sam Ravnborg
2007-10-15 15:40 ` Jörn Engel
2007-10-15 17:04 ` Doug Whitesell (LKML)
2007-10-15 17:04 ` Mark Gross
2007-10-15 18:30   ` Sam Ravnborg
2007-10-15 18:45     ` Mark Gross
2007-10-15 19:54     ` Giacomo Catenazzi
2007-10-16 20:06       ` Mark Gross
2007-10-16 20:09         ` Jan Engelhardt
2007-10-16 20:23           ` Rik van Riel [this message]
2007-10-16 20:25             ` Jan Engelhardt
2007-10-16 21:10               ` david
2007-10-16 21:30             ` david
2007-11-02  7:54             ` Giacomo Catenazzi
2007-10-16 20:31           ` Giacomo Catenazzi
2007-10-15 19:17   ` Alexey Dobriyan
2007-10-15 19:54     ` Folkert van Heusden
2007-10-16 20:10     ` Mark Gross
2007-10-16  0:39   ` david
2007-10-15 17:10 ` Zan Lynx
2007-10-15 17:23   ` Rik van Riel
2007-10-16  0:51   ` david
2007-10-15 17:30 ` Guilherme Amadio
2007-10-15 18:03   ` J. Bruce Fields
2007-10-17 17:45 ` Mark Gross
2007-10-18  4:51 ` Toshiharu Harada
2007-10-28 18:07 ` Pavel Machek
2007-10-28 18:57   ` Rafael J. Wysocki
2007-10-29 19:48   ` Lennart Sorensen
2007-10-29 20:19     ` Pavel Machek
2007-10-29 21:44       ` Lennart Sorensen
2007-11-03  3:08         ` Valdis.Kletnieks
2007-11-03  3:36           ` Rik van Riel
2007-11-03  9:44             ` Wander Winkelhorst
2007-11-03 10:05             ` david

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=20071016162310.1891914f@bree.surriel.com \
    --to=riel@surriel.com \
    --cc=cate@debian.org \
    --cc=jengelh@computergmbh.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@linux.intel.com \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®