sparc64/sab(4): Convert to ttylock/ttyunlock.

Merge thorpej-cfargs2.

Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass a

Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

show more ...

As discussed on tech-kern: define a new tty internal state flag: TS_KERN_ONLY

Implement it in a few tty drivers. If this flag is set, the underlying
hardware is used by another driver and userland h

As discussed on tech-kern: define a new tty internal state flag: TS_KERN_ONLY

Implement it in a few tty drivers. If this flag is set, the underlying
hardware is used by another driver and userland has no right to open
it. A few uses will appear soon in sys/dev/sun/sun{kbd,ms}.c.

show more ...

centralize the call unit / dialout macros

Convert sab_shutdown from deprecated shutdownhook_establish(9) API
to PMF(9) framework.

Tested on Ultra 60 with serial console.

Add d_discard to all struct cdevsw instances I could find.

All have been set to "nodiscard"; some should get a real implementation.

Change (mostly mechanically) every cdevsw/bdevsw I can find to use
designated initializers.

I have not built every extant kernel so I have probably broken at
least one build; however I've also found

Change (mostly mechanically) every cdevsw/bdevsw I can find to use
designated initializers.

I have not built every extant kernel so I have probably broken at
least one build; however I've also found and fixed some wrong
cdevsw/bdevsw entries so even if so I think we come out ahead.

show more ...

Remove unused variable

Only initialize when we are the first opener.

split auxio, ebus, psycho, sab.

also match the fujitsu sab: "FJSV,se" (from openbsd, pointed out by jdc)

Rename ttymalloc() to tty_alloc(), and ttyfree() to tty_free() for
consistency. Remove some unnecessary malloc.h inclusions as well.

various aprint_* fixes.

Re-do the previous check for the RSC console:
Do the check in sabtty_console_flags() and set a flag if we are an RSC port.
If we are an RSC port, note that the baud rate is 115200, but don't write a

Re-do the previous check for the RSC console:
Do the check in sabtty_console_flags() and set a flag if we are an RSC port.
If we are an RSC port, note that the baud rate is 115200, but don't write a
new value to the baud rate generator register, as this stops the console
working.

show more ...

Check for "ssp-console" and "ssp-control" properties.
If we find them, set the baud rate to 115200.
This allows the RSC to be the console on an E250:

sab1 at ebus0 addr 200000-20007f ipl 35: rev 3

Check for "ssp-console" and "ssp-control" properties.
If we find them, set the baud rate to 115200.
This allows the RSC to be the console on an E250:

sab1 at ebus0 addr 200000-20007f ipl 35: rev 3.2
sabtty2 at sab1 port 0: console i/o
sabtty3 at sab1 port 1

XXX; We should really check the baud rate properties and use those to set
our rates.

show more ...

use device_lookup_private to get softc
fixes build errors about pointer type mismatches in assignment

Properly fix the "hanging in tty" bug that was worked around with cv_wakeup()
some time again.

Use the softint API.

- Factor out too many copies of the same bit of tty code.
- Fix another tty signalling/wakeup problem.

Merge tty changes from the vmlocking branch.

Kill caddr_t; there will be some MI fallout, but it will be fixed shortly.

kgdb support for sabtty

More from Matt Fleming:

Adapt to KAUTH_DEVICE_TTY_PRIVSET and KAUTH_DEVICE_TTY_OPEN.

Adapt MD code to KAUTH_DEVICE_TTY_OPEN. Patch from Matt Fleming, thanks!