| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On some architectures, u_long isn't large enough for resource definitions.
Particularly, powerpc and arm allow 36-bit (or larger) physical addresses, but
type `long' is only 32-bit. This extends rman's resources to uintmax_t. With
this change, any resource can feasibly be placed anywhere in physical memory
(within the constraints of the driver).
Why uintmax_t and not something machine dependent, or uint64_t? Though it's
possible for uintmax_t to grow, it's highly unlikely it will become 128-bit on
32-bit architectures. 64-bit architectures should have plenty of RAM to absorb
the increase on resource sizes if and when this occurs, and the number of
resources on memory-constrained systems should be sufficiently small as to not
pose a drastic overhead. That being said, uintmax_t was chosen for source
clarity. If it's specified as uint64_t, all printf()-like calls would either
need casts to uintmax_t, or be littered with PRI*64 macros. Casts to uintmax_t
aren't horrible, but it would also bake into the API for
resource_list_print_type() either a hidden assumption that entries get cast to
uintmax_t for printing, or these calls would need the PRI*64 macros. Since
source code is meant to be read more often than written, I chose the clearest
path of simply using uintmax_t.
Tested on a PowerPC p5020-based board, which places all device resources in
0xfxxxxxxxx, and has 8GB RAM.
Regression tested on qemu-system-i386
Regression tested on qemu-system-mips (malta profile)
Tested PAE and devinfo on virtualbox (live CD)
Special thanks to bz for his testing on ARM.
Reviewed By: bz, jhb (previous)
Relnotes: Yes
Sponsored by: Alex Perez/Inertial Computing
Differential Revision: https://reviews.freebsd.org/D4544
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Off by default, build behaves normally.
WITH_META_MODE we get auto objdir creation, the ability to
start build from anywhere in the tree.
Still need to add real targets under targets/ to build packages.
Differential Revision: D2796
Reviewed by: brooks imp
|
| | |
|
| |\
| |/
|/| |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Requested by: Simon Gerraty <sjg@juniper.net>
|
| | |
| | |
| | |
| | |
| | |
| | | |
flag value is already exposed via dv_flags, just not the meaning of the
flags themselves. Use these constants to annotate devices that are
disabled or suspended in devinfo output.
|
| |/
|/|
| |
| | |
Reduce overlinking
|
|/
|
|
|
| |
PR: 191174
Submitted by: Franco Fichtner <franco@lastsummer.de>
|
|
|
|
| |
This allows compilers and static analyzers to do more thorough analysis.
|
|
|
|
|
|
|
|
| |
Although groff_mdoc(7) gives another impression, this is the ordering
most widely used and also required by mdocml/mandoc.
Reviewed by: ru
Approved by: philip, ed (mentors)
|
| |
|
|
|
|
|
|
|
| |
structure replication and improve manteneability.
Reviewed by: jhb, imp
Tested by: Riccardo Torrini <riccardo at torrini dot org>
|
|
|
|
|
|
|
| |
manager in hex vs decimal to 1000 from 100 so that IRQs are printed in
decimal.
MFC after: 3 days
|
| |
|
|
|
|
| |
Submitted by: ru
|
|
|
|
| |
options when -u is specified. Xref device(9) and devclass(9).
|
| |
|
|
|
|
| |
whose bus' provide this information.
|
|
|
|
|
|
|
|
| |
minted -v flag.
o Print devices that don't return a name as 'unknown' in -v mode.
# Yea! Now I wont think I have 10 different ISA network adapters in my
# laptop.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
o Minor grammar fixes.
o Sort SEE ALSO references, and add iostat(8).
o Delete punctuation at end of AUTHORS' section only line
Reviewed by: rwatson, Hiten Pandya <hiten@uk.FreeBSD.org>
|
|
|
|
|
|
| |
This is a whitespace only change.
Reviewed by: rwatson, Hiten Pandya <hiten@uk.FreeBSD.org>
|
|
|
|
|
|
|
| |
most useful new command added to FreeBSD 5.0, but maybe that's just
me :-).
Submitted by: Hiten Pandya <hiten@uk.FreeBSD.org>
|
|
|
|
| |
Pointed out by: bde
|
|
|
|
|
| |
PR: bin/32567
MFC after: 2 weeks
|
|
|
|
|
| |
These are not perfectly in agreement with each other style-wise, but they
are orders of orders of magnitude more consistent style-wise than before.
|
|
|
|
|
|
| |
Don't clobber CFLAGS by assigning to it using "=".
Fixed some style bugs.
|
|
serves as an example of libdevinfo usage.
|