add stmac read mac form eeprom

hc

2023-12-09 b22da3d8526a935aa31e086e63f60ff3246cb61c

 kernel/drivers/staging/unisys/Documentation/overview.txt
..
..
@@ -15,12 +15,12 @@
15
15
 * visorinput - keyboard and mouse
16
16
 
17
17
 These drivers conform to the standard Linux bus/device model described
18
-within Documentation/driver-model/, and utilize a driver named visorbus to
19
-present the virtual busses involved. Drivers in the 'visor*' driver set are
20
-commonly referred to as "guest drivers" or "client drivers".  All drivers
21
-except visorbus expose a device of a specific usable class to the Linux guest
22
-environment (e.g., block, network, or input), and are collectively referred
23
-to as "function drivers".
18
+within Documentation/driver-api/driver-model/, and utilize a driver named
19
+visorbus to present the virtual busses involved. Drivers in the 'visor*'
20
+driver set are commonly referred to as "guest drivers" or "client drivers".
21
+All drivers except visorbus expose a device of a specific usable class to the
22
+Linux guest environment (e.g., block, network, or input), and are collectively
23
+referred to as "function drivers".
24
24
 
25
25
 The back-end for each device is owned and managed by a small,
26
26
 single-purpose service partition in the s-Par firmware, which communicates
..
..
@@ -141,7 +141,7 @@
141
141
 -----------------------------------
142
142
 
143
143
 Because visorbus is a standard Linux bus driver in the model described in
144
-Documentation/driver-model/, the hierarchy of s-Par virtual devices is
144
+Documentation/driver-api/driver-model/, the hierarchy of s-Par virtual devices is
145
145
 published in the sysfs tree beneath /bus/visorbus/, e.g.,
146
146
 /sys/bus/visorbus/devices/ might look like:
147
147