From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Automating the process of building kernel pci drivers
Date: Tue, 19 Apr 2005 09:08:20 -0400 [thread overview]
Message-ID: <1113916100.9616.146.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <426479D2.1010206@securesystem.info>
[-- Attachment #1: Type: text/plain, Size: 867 bytes --]
On Tue, 2005-04-19 at 12:24 +0900, Chris White wrote:
> 1) What if the device has no module?
> 2) Do we generate it for a specific kernel version for the livecd, or
> try multiple ones?
> 3) Do arches have any issues?
> 4) Is it possible for two modules to hold over the same device and
> possibly conflict with each other?
> 5) Could certain modules cause other modules to fail? Does a short
> rules list need to be created to prevent problematic combinations?
> 6) How should we approach the userspace program? Should we simply
> extend genkernel or go with something more specialized?
7) What if you bought the device after building your kernel?
8) What if the device is external and not connected?
9) Why are we even bothering with this?
--
Chris Gianelloni
Release Engineering - Strategic Lead/QA Manager
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-04-19 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 3:24 [gentoo-releng] Automating the process of building kernel pci drivers Chris White
2005-04-19 7:19 ` Daniel Drake
2005-04-19 13:08 ` Chris Gianelloni [this message]
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=1113916100.9616.146.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-releng@lists.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