| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
posix standard on the topic.
|
|
|
|
| |
posix standard on the topic.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of binutils. For all architectures and object file formats,
".p2align n" aligns to the next multiple of 2**n. Thus for FreeBSD,
it does exactly the same thing as the traditional ".align".
The old ".align" directive has different meanings in different
object formats, and even in different variants of a.out. Sometimes
is aligns to a multiple of n, and other times it aligns to a multiple
of 2**n. ".p2align" is preferable for use in assembly language
sources, since it makes them more portable to object formats other
than a.out.
|
| |
|
| |
|
|
|
|
| |
Submitted by: Yoshiaki Uchikawa <yoshiaki@kt.rim.or.jp>
|
|
|
|
| |
posix standard on the topic.
|
|
|
|
| |
posix standard on the topic.
|
| |
|
|
|
|
|
|
|
|
|
| |
I was not sure whether the fs_id fields should be printed in the clear
in case of sniffing over a network login etc. It might be an idea
to have somebody with spare time go through and find any other missing
fields that should be reported.
Definate 2.2.x/2.1.x candidate since it breaks the build.
|
|
|
|
|
| |
ddb isn't necessarily fatal. You can now do silly things like
`call vprint' and `show map' without losing control.
|
|
|
|
| |
fatal.
|
|
|
|
| |
isn't fatal. Backed out rev.1.6, which handled special cases of this.
|
|
|
|
|
|
|
|
| |
functions if DDB is available. The remaining occurences are usually
only inlined and thus not available in DDB.
I'm sure Bruce will have 23 additions to these 30 lines of code, but
at least it's a starting point. ;-)
|
|
|
|
|
| |
Fixed #includes in synopsis to declare the prototype in the synopsis.
Fixed stale types in description of struct dirent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
change typematic rate, or the X server (XFree86 or Accelerated X)
starts up.
So far, there have been two independent reports from Dell Latitude XPi
notebook/laptop owners. The Latitude seems to be the only system which
suffers from this problem. (I don't know the problem is with the
entire Latitude line or with only some Latitude models) No problem
report has been heard about other systems (I certainly cannot
reproduce the problem in my -current and 2.2 systems).
In 3.0-CURRENT, 2.2-RELEASE and 2.2-GAMMA-970310, when programming the
keyboard LED/repeat-rate, `set_keyboard()' in `syscons' tells the
keyboard controller not to generate keyboard interrupt (IRQ1) and then
enable tty interrupts, expecting the keyboard interrupt doesn't occur.
It appears that somehow Latitude's keyboard controller still generates
the keyboard interrupt thereafter, and `set_keyboard()' doesn't see
the return code from the keyboard because it is consumed by the
keyboard interrupt handler.
The patch entirely disables tty interrupts while setting LED and
typematic rate in `set_keyboard()', making the routine behave more
like the previous versions of `syscons' (versions in 2.1.X and
2.2-ALPHA, -BETA, and some -GAMMAs). The reporter said this patch
eliminated the problem.
(I also found another typo/bug, but the reporter and I found that it
wasn't the cause of the problem...)
This should go into RELENG_2_2.
|
|
|
|
| |
from the environment.
|
|
|
|
| |
is is really probe routine task (return -1 for no ports)
|
|
|
|
|
|
| |
non-standard and not used. "port auto" is equal to "port?" or missing "port"
keyword now. "port none" is really probe routine task (return -1 for
no ports).
|
|
|
|
|
|
| |
ports. This option will be automatically set/cleraed when mount is run
without/with the -n option.
Reviewed by: Doug Rabson
|
| |
|
|
|
|
| |
Pointed out by: bde
|
| |
|
|
|
|
| |
Submitted by: Choi Jun Ho <choi.junho@jazz.snu.ac.kr>
|
| |
|
|
|
|
| |
Submitted by: Dmitrij Tejblum <dima@tejblum.dnttm.rssi.ru>, PR#3076
|
| |
|
| |
|
|
|
|
| |
Submitted by: Philippe Charnier
|
| |
|
| |
|
|
|
|
| |
documented in the DESCRIPTION section.
|
|
|
|
|
|
| |
and conflict with sb0 irq.
NOTE: existen configurations require "conflicts" adding to sbmidi0 now
|
|
|
|
| |
Pass configured irq back to isa
|
|
|
|
|
|
|
| |
and conflict with sb0 happens.
NOTE: it affects existen configurations, add "conflicts" to sbxvi0 line
if you see probe error
|
| |
|
| |
|
| |
|
|
|
|
| |
Forgotten by: joerg :)
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Now port ommiting is equal to port "none" not to port 0
|
|
|
|
| |
Submitted by: Choi Jun Ho <choi.junho@jazz.snu.ac.kr>
|
| |
|