stand: Update comment about devdesc
How devdesc is used is opaque until much code is read. Give a more useful description of the theory behind it here. Sponsored by: Netflix
This commit is contained in:
+8
-3
@@ -170,9 +170,14 @@ extern struct devsw netdev;
|
|||||||
extern int errno;
|
extern int errno;
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Generic device specifier; architecture-dependent
|
* Generic device specifier; architecture-dependent versions may be larger, but
|
||||||
* versions may be larger, but should be allowed to
|
* should be allowed to overlap. The larger device specifiers store more data
|
||||||
* overlap.
|
* than can fit in the generic one that's gleaned after parsing the device
|
||||||
|
* string, or used in some cases to indicate wildcards that match a variety of
|
||||||
|
* situations based on what's on the drive itself rather than what the progammer
|
||||||
|
* might know in advance. Information about open files is stored in d_opendata,
|
||||||
|
* though what's passed into the open routine may differ from what's present
|
||||||
|
* after the open on some configurations.
|
||||||
*/
|
*/
|
||||||
struct devdesc {
|
struct devdesc {
|
||||||
struct devsw *d_dev;
|
struct devsw *d_dev;
|
||||||
|
|||||||
Reference in New Issue
Block a user