Up to [cvs.NetBSD.org] / src / sys / fs / udf
Request diff between arbitrary revisions
Default branch: MAIN
Current tag: jmcneill-pm
Revision 1.36.4.5 / (download) - annotate - [select for diffs], Mon Dec 3 16:14:45 2007 UTC (16 years, 3 months ago) by joerg
Branch: jmcneill-pm
Changes since 1.36.4.4: +12 -13
lines
Diff to previous 1.36.4.4 (colored) to branchpoint 1.36 (colored) next main 1.37 (colored)
Sync with HEAD.
Revision 1.36.4.4 / (download) - annotate - [select for diffs], Tue Nov 27 19:37:56 2007 UTC (16 years, 4 months ago) by joerg
Branch: jmcneill-pm
Changes since 1.36.4.3: +5 -6
lines
Diff to previous 1.36.4.3 (colored) to branchpoint 1.36 (colored)
Sync with HEAD. amd64 Xen support needs testing.
Revision 1.36.4.3 / (download) - annotate - [select for diffs], Wed Oct 31 23:14:09 2007 UTC (16 years, 5 months ago) by joerg
Branch: jmcneill-pm
Changes since 1.36.4.2: +3 -2
lines
Diff to previous 1.36.4.2 (colored) to branchpoint 1.36 (colored)
Sync with HEAD.
Revision 1.36.4.2 / (download) - annotate - [select for diffs], Fri Oct 26 15:48:24 2007 UTC (16 years, 5 months ago) by joerg
Branch: jmcneill-pm
Changes since 1.36.4.1: +21 -24
lines
Diff to previous 1.36.4.1 (colored) to branchpoint 1.36 (colored)
Sync with HEAD. Follow the merge of pmap.c on i386 and amd64 and move pmap_init_tmp_pgtbl into arch/x86/x86/pmap.c. Modify the ACPI wakeup code to restore CR4 before jumping back into kernel space as the large page option might cover that.
Revision 1.36.4.1 / (download) - annotate - [select for diffs], Tue Oct 2 18:28:56 2007 UTC (16 years, 6 months ago) by joerg
Branch: jmcneill-pm
Changes since 1.36: +13 -10
lines
Diff to previous 1.36 (colored)
Sync with HEAD.
Revision 1.36 / (download) - annotate - [select for diffs], Sun Jul 29 13:31:11 2007 UTC (16 years, 8 months ago) by ad
Branch: MAIN
CVS Tags: yamt-x86pmap-base,
nick-csl-alignment-base5,
matt-mips64-base,
hpcarm-cleanup
Branch point for: yamt-x86pmap,
matt-mips64,
matt-armv6,
jmcneill-pm
Changes since 1.35: +2 -5
lines
Diff to previous 1.35 (colored)
It's not a good idea for device drivers to modify b_flags, as they don't need to understand the locking around that field. Instead of setting B_ERROR, set b_error instead. b_error is 'owned' by whoever completes the I/O request.