[gentoo-user] Making changes to a statically build driver
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
Re: [gentoo-user] Making changes to a statically build driver
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.tay...@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 -- If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have one idea and we exchange these ideas, then each of us will have two ideas. - George Bernard Shaw
Re: [gentoo-user] Making changes to a statically build driver
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.tay...@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
Re: [gentoo-user] Making changes to a statically build driver
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 ~ # 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.tay...@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
