public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "W.Kenworthy" <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Making changes to a statically build driver
Date: Fri, 06 Mar 2009 11:28:56 +0900	[thread overview]
Message-ID: <1236306536.8451.2.camel@bunyip.localdomain> (raw)
In-Reply-To: <543f3b9c0903051817lb850d5fo3cda2efb94490c69@mail.gmail.com>

Set something that will show on the modinfo command?

I dont have e1000, but this a coda.ko example

bunyip ~ # modinfo coda 
filename:       /lib/modules/2.6.27-gentoo-r4/kernel/fs/coda/coda.ko
version:        6.6
license:        GPL
alias:          char-major-67-*
description:    Coda Distributed File System VFS interface
author:         Jan Harkes, Peter J. Braam
srcversion:     88DB5609F61269AF835BA05
depends:        
vermagic:       2.6.27-gentoo-r4 preempt mod_unload modversions
PENTIUMM 
bunyip ~ #

Billk




On Thu, 2009-03-05 at 23:17 -0300, Francisco Ares wrote:
> Never made such thing, so just a guess: maybe a log entry on some
> event, like link up - at that time, probably, the log engine is
> already up and running.
> 
> Francisco
> 
> On Thu, Mar 5, 2009 at 8:16 PM, Ezra Taylor <ezra.taylor@gmail.com> wrote:
> > Hello all:
> >                I made some changes to the e1000 kernel driver.  I then
> > recompiled the kernel without any issue.  How can I tell if the change
> > actually went through?  Again, this driver has been statically built into
> > the kernel.  Is there a way to test that a change went through without have
> > to setup a test environment?
> >
> > --
> > Ezra Taylor
> >
> 
> 
> 




  reply	other threads:[~2009-03-06  2:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-05 23:16 [gentoo-user] Making changes to a statically build driver Ezra Taylor
2009-03-06  2:17 ` Francisco Ares
2009-03-06  2:28   ` W.Kenworthy [this message]
2009-03-06  2:31     ` W.Kenworthy

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=1236306536.8451.2.camel@bunyip.localdomain \
    --to=billk@iinet.net.au \
    --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