1 |
I missed the bit where you said it was staic in the kernel - that |
2 |
besides, make it print something during load. |
3 |
|
4 |
Billk |
5 |
|
6 |
On Fri, 2009-03-06 at 11:28 +0900, W.Kenworthy wrote: |
7 |
> Set something that will show on the modinfo command? |
8 |
> |
9 |
> I dont have e1000, but this a coda.ko example |
10 |
> |
11 |
> bunyip ~ # modinfo coda |
12 |
> filename: /lib/modules/2.6.27-gentoo-r4/kernel/fs/coda/coda.ko |
13 |
> version: 6.6 |
14 |
> license: GPL |
15 |
> alias: char-major-67-* |
16 |
> description: Coda Distributed File System VFS interface |
17 |
> author: Jan Harkes, Peter J. Braam |
18 |
> srcversion: 88DB5609F61269AF835BA05 |
19 |
> depends: |
20 |
> vermagic: 2.6.27-gentoo-r4 preempt mod_unload modversions |
21 |
> PENTIUMM |
22 |
> bunyip ~ # |
23 |
> |
24 |
> Billk |
25 |
> |
26 |
> |
27 |
> |
28 |
> |
29 |
> On Thu, 2009-03-05 at 23:17 -0300, Francisco Ares wrote: |
30 |
> > Never made such thing, so just a guess: maybe a log entry on some |
31 |
> > event, like link up - at that time, probably, the log engine is |
32 |
> > already up and running. |
33 |
> > |
34 |
> > Francisco |
35 |
> > |
36 |
> > On Thu, Mar 5, 2009 at 8:16 PM, Ezra Taylor <ezra.taylor@×××××.com> wrote: |
37 |
> > > Hello all: |
38 |
> > > I made some changes to the e1000 kernel driver. I then |
39 |
> > > recompiled the kernel without any issue. How can I tell if the change |
40 |
> > > actually went through? Again, this driver has been statically built into |
41 |
> > > the kernel. Is there a way to test that a change went through without have |
42 |
> > > to setup a test environment? |
43 |
> > > |
44 |
> > > -- |
45 |
> > > Ezra Taylor |
46 |
> > > |
47 |
> > |
48 |
> > |
49 |
> > |
50 |
> |
51 |
> |