I missed the bit where you said it was staic in the kernel - that
besides, make it print something during load.
Billk
On Fri, 2009-03-06 at 11:28 +0900, W.Kenworthy wrote:
> Set something that will show on the modinfo command?
>
> I dont have e1000, but this a coda.ko example
>
> bunyip ~ # mod
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
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 wrote:
> Hello all:
> I made some changes to the e1000 kernel driver. I
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 h
4 matches
Mail list logo