Re: com(4) dialout device behavior change?

["John D. Baker" <jdbaker%consolidated.net@localhost>]

On Sun, 14 Apr 2019, John D. Baker wrote:

> So it appears my kernel paring has elided something that is now
> necessary.

Comparing my custom config for netbsd-8 versus -current, the only
obvious relevant difference is how "options COMPAT_XX" is handled.
I tend to aggressively elide all COMPAT_XX earlier than the immediate
previous release, but perhaps:

  include "arch/amd64/conf/GENERIC"
  [...]
  no options COMPAT_15

Is now eliding too much?  Since the old "options COMPAT_XX" are now
replaced with "include conf/compat_netbsdXX.config" which bakes in all
compat features for the given "XX" forward ("15" in amd64 GENERIC), and
I elided it as shown above, perhaps something important for serial ports
got left out.

It appears that I can simply give "options COMPAT_XX" for any given XX
once I've turned off COMPAT_15.  Then I can test kernels and adjust to
find the necessary minimum COMPAT_XX I need.


The only other differences in the configs are related to eliding added
drivers for devices I don't and likely will never have.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645