1 What: /sys/module/pch_phub/drivers/. 1 What: /sys/module/pch_phub/drivers/.../pch_mac
2 Date: August 2010 2 Date: August 2010
3 KernelVersion: 2.6.35 3 KernelVersion: 2.6.35
4 Contact: masa-korg@dsn.okisemi.com 4 Contact: masa-korg@dsn.okisemi.com
5 Description: Write/read GbE MAC address. 5 Description: Write/read GbE MAC address.
6 6
7 What: /sys/module/pch_phub/drivers/. 7 What: /sys/module/pch_phub/drivers/.../pch_firmware
8 Date: August 2010 8 Date: August 2010
9 KernelVersion: 2.6.35 9 KernelVersion: 2.6.35
10 Contact: masa-korg@dsn.okisemi.com 10 Contact: masa-korg@dsn.okisemi.com
11 Description: Write/read Option ROM data. 11 Description: Write/read Option ROM data.
12 12
13 13
14 What: /sys/module/ehci_hcd/drivers/. 14 What: /sys/module/ehci_hcd/drivers/.../uframe_periodic_max
15 Date: July 2011 15 Date: July 2011
16 KernelVersion: 3.1 16 KernelVersion: 3.1
17 Contact: Kirill Smelkov <kirr@mns.spb.ru 17 Contact: Kirill Smelkov <kirr@mns.spb.ru>
18 Description: Maximum time allowed for perio 18 Description: Maximum time allowed for periodic transfers per microframe (μs)
19 19
20 Note: 20 Note:
21 USB 2.0 sets maximum allowed 21 USB 2.0 sets maximum allowed time for periodic transfers per
22 microframe to be 80%, that i 22 microframe to be 80%, that is 100 microseconds out of 125
23 microseconds (full microfram 23 microseconds (full microframe).
24 24
25 However there are cases, whe 25 However there are cases, when 80% max isochronous bandwidth is
26 too limiting. For example tw 26 too limiting. For example two video streams could require 110
27 microseconds of isochronous 27 microseconds of isochronous bandwidth per microframe to work
28 together. 28 together.
29 29
30 Through this setting it is pos 30 Through this setting it is possible to raise the limit so that
31 the host controller would allo 31 the host controller would allow allocating more than 100
32 microseconds of periodic bandw 32 microseconds of periodic bandwidth per microframe.
33 33
34 Beware, non-standard modes are 34 Beware, non-standard modes are usually not thoroughly tested by
35 hardware designers, and the ha 35 hardware designers, and the hardware can malfunction when this
36 setting differ from default 10 36 setting differ from default 100.
37 37
38 What: /sys/module/*/{coresize,initsi 38 What: /sys/module/*/{coresize,initsize}
39 Date: Jan 2012 39 Date: Jan 2012
40 KernelVersion: 3.3 40 KernelVersion: 3.3
41 Contact: Kay Sievers <kay.sievers@vrfy.o 41 Contact: Kay Sievers <kay.sievers@vrfy.org>
42 Description: Module size in bytes. 42 Description: Module size in bytes.
43 43
44 What: /sys/module/*/initstate 44 What: /sys/module/*/initstate
45 Date: Nov 2006 45 Date: Nov 2006
46 KernelVersion: 2.6.19 46 KernelVersion: 2.6.19
47 Contact: Kay Sievers <kay.sievers@vrfy.o 47 Contact: Kay Sievers <kay.sievers@vrfy.org>
48 Description: Show the initialization state( 48 Description: Show the initialization state(live, coming, going) of
49 the module. 49 the module.
50 50
51 What: /sys/module/*/taint 51 What: /sys/module/*/taint
52 Date: Jan 2012 52 Date: Jan 2012
53 KernelVersion: 3.3 53 KernelVersion: 3.3
54 Contact: Kay Sievers <kay.sievers@vrfy.o 54 Contact: Kay Sievers <kay.sievers@vrfy.org>
55 Description: Module taint flags: 55 Description: Module taint flags:
56 == ================== 56 == =====================
57 P proprietary module 57 P proprietary module
58 O out-of-tree module 58 O out-of-tree module
59 F force-loaded modul 59 F force-loaded module
60 C staging driver mod 60 C staging driver module
61 E unsigned module 61 E unsigned module
62 == ================== 62 == =====================
63 <<
64 What: /sys/module/grant_table/parame <<
65 Date: July 2023 <<
66 KernelVersion: 6.5 but backported to all supp <<
67 Contact: Xen developer discussion <xen-d <<
68 Description: Read and write number of grant <<
69 <<
70 Note: Future versions of Xen a <<
71 interface for controlling the <<
72 or may not need it at all. <<
73 Users: Qubes OS (https://www.qubes-os <<
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.