public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel Modules
Date: Thu, 09 Jun 2011 13:37:02 +0200	[thread overview]
Message-ID: <29734258.XRhzE4u60j@localhost> (raw)
In-Reply-To: <4DF0A5FA.1020602@gmail.com>

On Thursday 09 June 2011 11:52:42 Ignas Anikevicius wrote:
> Hello list,
> 
> I was wondering if it is possible to have a tool with which it would be
> possible to have external modules installed for _all_ kernel versions in
> my computer. Now I am using 2.6.38 kernel, but would like to try 2.6.39
> and the thing is that I would like to have tp_smapi and phc-intel
> modules in both kernels. Is it possible to have it without any serious
> hacking?
> 
> I have only 3 ideas how I could achieve that:
> * Making a custom ebuild, which would build the modules, but install
> itself as a different package depending on the kernel version (eg
> tp_smapi-2.6.39-gentoo)?
> * Making a custom ebuild, which would build the modules for all kernel
> versions in one go... (is this possible?)
> * patching the gentoo-sources each time.
> 
> Is any of these solutions sensible?
> 
> Cheers,
> Ignas

why not emerging them several times with linux pointing to the different 
kernels?

I that does not work:
ebuild .... unpack
ebuild .... compile
ebuild .... install
cp .ko from image directory to modules directory
depmod -ae


-- 
#163933



      parent reply	other threads:[~2011-06-09 11:39 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 10:52 [gentoo-user] Kernel Modules Ignas Anikevicius
2011-06-09 11:06 ` YoYo Siska
2011-06-09 11:06 ` Alan McKinnon
2011-06-09 12:12   ` Ignas Anikevicius
2011-06-09 17:32     ` [gentoo-user] " Nikos Chantziaras
2011-06-09 18:18       ` Alan McKinnon
2011-06-09 18:52         ` Bill Longman
2011-06-09 19:06           ` Alan McKinnon
2011-06-10  9:49           ` Nikos Chantziaras
2011-06-10 17:41             ` Dale
     [not found]               ` <BANLkTinmmzhzXXJ6Sq1pSTGtM5prJ7dq3Q@mail.gmail.com>
2011-06-10 19:08                 ` Dale
2011-06-10 19:46                   ` Nikos Chantziaras
2011-06-10 20:05                     ` Dale
2011-06-10 20:31                       ` Paul Hartman
2011-06-10 20:55                         ` Dale
2011-06-15 16:07                         ` Peter Humphrey
2011-06-15 16:25                           ` Neil Bothwick
2011-06-15 18:05                             ` Peter Humphrey
2011-06-16  7:14                               ` [gentoo-user] " Stroller
2011-06-10 20:38                   ` [gentoo-user] " Paul Hartman
2011-06-10 21:34                 ` Mick
2011-06-10 21:42                   ` Paul Hartman
2011-06-10 21:55                     ` Mick
2011-06-09 19:03         ` Dale
2011-06-09 19:37           ` Alan McKinnon
2011-06-09 19:44             ` YouTube Support
2011-06-09 20:23               ` [gentoo-user] Re: umm, google.... WAS: " Alan McKinnon
2011-06-09 21:05                 ` Dale
2011-06-09 20:06             ` [gentoo-user] " Paul Hartman
2011-06-09 20:44               ` Mick
2011-06-15 16:10                 ` Peter Humphrey
2011-06-09 11:37 ` Volker Armin Hemmann [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=29734258.XRhzE4u60j@localhost \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@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