wireguard-openbsd/sys/arch/alpha/include/disklabel.h, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/alpha/include/disklabel.h?h=jd%2Fqueueboosts 2015-09-30T14:57:03Z Use consistant whitespace/comments for #define'ing LABELSECTOR, 2015-09-30T14:57:03Z krw krw@openbsd.org 2015-09-30T14:57:03Z urn:sha1:1e913dd52d0a3acac5504d17d3bc153b4a45476e LABELOFFSET and MAXPARTITIONS. Easier on the eye when scanning through all these files. No functional change. b_cylinder does not need to be set on the callpath down into drivers. 2007-06-20T18:15:43Z deraadt deraadt@openbsd.org 2007-06-20T18:15:43Z urn:sha1:c326f117376551b79ce73d7cceafef3cc69e5a5b cpu_disklabel can go away, since nothing anymore needs to use it; ok miod Eliminate a few straggling 'labelsector' field declarations from 2007-06-17T15:05:08Z krw krw@openbsd.org 2007-06-17T15:05:08Z urn:sha1:475f37ce2d9f1ce9a442ae61c0e670b645b1af36 cpu_disklabel's. 'labelsector' is not used anywhere according to grep. 'go for it' deraadt@ significantly simplified disklabel infrastructure. MBR handling becomes MI 2007-06-17T00:27:24Z deraadt deraadt@openbsd.org 2007-06-17T00:27:24Z urn:sha1:eb1f9bf65ef19e4cc9281b6f102ab5817a8b7945 to support hotplug media on most architectures. disklabel setup and verification done using new helper functions. Disklabels must *always* have a correct checksum now. Same code paths are used to learn on-disk location disklabels, to avoid new errors sneaking in. Tested on almost all cases, testing help from todd, kettenis, krw, otto, dlg, robert, gwk, drahn No need for two *LABELSECTOR and *LABELOFFSET defines that mean the 2007-06-10T05:42:48Z krw krw@openbsd.org 2007-06-10T05:42:48Z urn:sha1:41fe0d730e4e3c9a18d37d07c71c211e03b9f43d same thing. Keep LABELSECTOR and LABELOFFSET and nuke ALPHA_LABELSECTOR and ALPHA_LABELOFFSET. Kernel still compiles and boots. Superfluidity pointed out by deraadt@. Try again with local variable to avoid alignment issues. 2006-10-20T23:47:42Z krw krw@openbsd.org 2006-10-20T23:47:42Z urn:sha1:bc5ec36a7c8762d695ea08a85b0dcfc297f19996 "The dosparts member of cpu_disklabel was not used for any persistant data. Eliminate it, and just use the data being read in while processing MBR and EBR records. Should be no functional change. ok weingart@ deraadt@" back out disksubr changes ... since they violate strict alignment on 2006-10-18T20:09:37Z deraadt deraadt@openbsd.org 2006-10-18T20:09:37Z urn:sha1:4a1e7e62c8bcf4152725906aaf00c187ad5744c7 some architectures (kaboom); that will be fixed in the next iteration hopefully! The dosparts member of cpu_disklabel was not used for any persistant 2006-10-17T23:42:37Z krw krw@openbsd.org 2006-10-17T23:42:37Z urn:sha1:dc261d6ca42f1c861da655a180d712770c05d57b data. Eliminate it, and just use the data being read in while processing MBR and EBR records. Should be no functional change. ok weingart@ deraadt@ Zap bad144 bad sector info in disklabels. Sparsely used if at all for 2006-10-04T00:52:55Z krw krw@openbsd.org 2006-10-04T00:52:55Z urn:sha1:6c24d64484a78f496223329ba9cfbd6fd5f25991 a few obsolete and easily replaced disk models. And didn't work anyway according to Bob, who has tried. ok beck@ Remove DLT_* logic from Alpha as well, being careful to keep the 2006-07-09T21:00:17Z krw krw@openbsd.org 2006-07-09T21:00:17Z urn:sha1:7838db20e928cbb2b8e6ab542be2ce8a19cf4f76 checksumming of the native disklabel. No functional change.