H. Peter Anvin wrote:
Greg KH wrote:
But it ignored the fact that I said I didn't want this binary file in
sysfs :)
Please take Eric's suggestion and split it up into the different pieces.
Some of the fields can be binary files, as they come directly from the
firmware, but the others should be text.
But PLEASE include the full structure as a ready-to-eat object. PLEASE.
I should clarify this.
By all means go ahead and provide broken-out fields where it makes
sense. However:
- this *IS* a structure defined by protocol, and which, for all users
except the 16-bit entry, comes from outside the kernel (bootloader or
firmware.)
- a newer kernel version can add fields to this structure, but can never
remove them. This would cause a potential information loss if the
current kernel doesn't have all fields available.
- the binary structure is the format that the majority of users will need.
This is directly analogous to how we treat identity information in IDE,
or PCI configuration space -- some fields are pre-digested, but the
entire raw information is also available.
-hpa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
