- the cap field is a u_int8_t, so none of the defined flags would fit in.
Looks like nobody had a drive using 16 bytes commands.
- the ACAP_DRQ_* flags are all wrong. Just remove them and use the definitions
from ata/atareg.h, there's no need to duplicate theses. The effect of this
was that we were always polling for the command phase, even for drives
with interrupt DRQ. This didn't break until the code was changed to support
shared interrupts.
Should fix the lookup problems or 'boot hangs' reported by some users, and
kern/7111.
needs to have the diagnostic list explained, and the media support
list filled out before it gets pulled up to the 1.4 branch.
However, it's here to answer PR#6870
hasn't been seen by anyone yet, why encourage its use by defining it?
2) Indicate in a comment that the NetBSD define is now frozen, will
never again be incremented, and may even be deprecated. Indicate
yet again that all new code must use __NetBSD_Version__
clean bit. This is somewhat bogus as RAID 0 does not have any parity,
but is a slightly cleaner than other solutions, and makes the handling
of clean bits for RAID 0 consistent with the handling of clean bits at
other RAID levels.
once we determined the rigth protocol to use, recall get_nfs_version()
so that the last RPC call was a successfull one. Otherwise with a SunOS 4.1.4
server (which doesn't accept TCP mounts) UDP mounts would fail.
The problem is that if "sl" is a symbolic link, a lookup on "sl/"
will be flagged as the last component. Thus VOP_LOOKUP will lock
the parent directory if LOCKPARENT is set. In order for the symbolic
link to be resolved, this lock needs to be released. namei() would
test for this by checking if ni_pathlen == 1, which it wouldn't as
"/" is left in the name, and namei() would not unlock the parent.
The next call to lookup() to resolve the symbolic link would fail
as the parent was still locked.
the architecture manual, as boot(8) does that and only boot(8) provides
the necessary context to understand why the Alpha Architecture
Reference Manual is relevant.
page for now isn't the descriptive text, it's the comments in the
roff source which describe an outline of what the descriptive text
should look like. also useful is the one stop shopping list of
non-deprecated bootstrap-related commands and files.
initialized). This lock also protects the "next drain candidate" pointer.
XXX There is still one locking protocol problem, which should not be
a problem in practice, but is still marked as an issue in the code anyhow.
agc