Lines Matching refs:order
1567 >0xc byte 00 \b, DOS 3.3 sector order
1570 >0xc byte 01 \b, ProDOS sector order
1627 # that I could find. The 1 and 2 really mean "order in which you defined
1639 # row- or column-order recalculation; the A or M means automatic or manual
1882 # byte order as the machine running "file" with "cpio archive", and
1883 # to indicate archives produced on machines with the opposite byte order
1904 # They were written with binary values in host byte order, and
3707 # "VAX-order" and "VAX-order2"?
3711 0 short 03401 VAX-order 68K Blit (standalone) executable
3714 0 short 03001 VAX-order 68k Blit mpx/mux executable
4252 # XXX - what byte order does the Clipper use?
4502 # This magic number is byte-order-independent.
4507 # byte-order independent, and one of which is byte-order dependent?
5188 # Hash 1.85/1.86 databases store metadata in network byte order.
5189 # Btree 1.85/1.86 databases store the metadata in host byte order.
5190 # Hash and Btree 2.X and later databases store the metadata in host byte order.
5197 >>4 belong >0 (Hash, version %d, native byte-order)
5211 >>4 belong >0 (Hash, version %d, native byte-order)
5214 >4 long >0 (Btree, version %d, native byte-order)
5221 >16 long >0 (Hash, version %d, native byte-order)
5228 >16 long >0 (Btree, version %d, native byte-order)
5235 >16 long >0 (Queue, version %d, native byte-order)
5243 >16 long >0 (Log, version %d, native byte-order)
5883 # We specify both byte orders in order to recognize byte-swapped dumps.
6074 # We have to check the byte order flag to see what byte order all the
6367 >5 byte 0 invalid byte order
6399 # XXX - needs to have the byte order specified (NS32K was little-endian,
9084 # All new-style FreeBSD magic numbers are in host byte order (i.e.,
9200 # 28: low order byte of the current PTD entry, always 0 since the
10278 # XXX - somebody should figure out whether any byte order needs to be
10289 # practice in order to avoid collisions.
10310 # The "misc" stuff needs a byte order; the archives look suspiciously
10320 0 long 01203604016 TML 0123 byte-order format
10321 0 long 01702407010 TML 1032 byte-order format
10322 0 long 01003405017 TML 2301 byte-order format
10323 0 long 01602007412 TML 3210 byte-order format
10573 # Unfortunately, HP-UX uses corehead blocks without specifying the order
10579 # The only observed order in real core files is KERNEL, EXEC, FORMAT, PROC
10580 # but we include all 6 variations of the order of the first 3, and
12528 # "long" magic is a better practice in order to avoid collisions.
13078 # yes, this is separate from the low-order magic number bit
14206 # XXX - byte order?
14244 # XXX - byte order?
15545 >>0x400A string \0\0\0\0\0\0 MSX MegaROM with nonstandard page order
15553 >>0x800A string \0\0\0\0\0\0 MSX MegaROM with nonstandard page order
15561 >0x3C008 string \0\0\0\0\0\0\0\0 MSX MegaROM with nonstandard page order
15739 # All new-style magic numbers are in network byte order.
16132 # We have to check the byte order flag to see what byte order all the
16157 >5 byte 0 invalid byte order
16170 >>18 leshort 1 AT&T WE32100 - invalid byte order,
16171 >>18 leshort 2 SPARC - invalid byte order,
16173 >>18 leshort 4 Motorola 68000 - invalid byte order,
16174 >>18 leshort 5 Motorola 88000 - invalid byte order,
16177 >>18 leshort 8 MIPS R3000_BE - invalid byte order,
16178 >>18 leshort 9 Amdahl - invalid byte order,
16180 >>18 leshort 11 RS6000 - invalid byte order,
16181 >>18 leshort 15 PA-RISC - invalid byte order,
16203 >>18 beshort 3 Intel 80386 - invalid byte order,
16206 >>18 beshort 6 Intel 80486 - invalid byte order,
16210 >>18 beshort 10 MIPS R3000_LE - invalid byte order,
16619 # XXX - byte order?
16734 >4 byte >0 (net-order %d)
17327 # XXX - byte order? Paging Hokey....
17540 # XXX - byte order?
18298 # XXX - byte order?
19065 # XXX - byte order?
19817 # XXX - byte order for screen images?
