-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathTRAIN_00197.eml
34 lines (28 loc) · 1.25 KB
/
TRAIN_00197.eml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
NoneNone> On Mon, Apr 5, 2010 at 8:53 AM, Stephen Powell wrote:
>> On Sun, 4 Apr 2010 17:36:03 -0400 (EDT), Lubos Rendek wrote:
>>>
>>> thanks guys for this.. Now what is the best way to link modules to a
>>> specific hardware. for example my lsmod shows that I use 'ecb' module.
>>> For someone like me this name does not say much. Is there a way to
>>> find which module belongs to which piece of hardware?
>>
>> =C2=A0 /sbin/modinfo ecb
>>
>> The "description" line is helpful of course. =C2=A0And the "alias" lines
>> identify which pieces of hardware will cause the module to be loaded,
>> for most device drivers. =C2=A0(Some older device drivers don't have any
>> internal aliases and require help from external aliases to load
>> automatically when the corresponding hardware device is detected.
>
> thanks Stephen this is exactly what I was looking for. :-)
You're welcome. But please don't "top post".
http://en.wikipedia.org/wiki/Top_posting
--=20
.''`. Stephen Powell <[email protected]>
: :' :
`. `'`
`-
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]