Re: com(4) dialout device behavior change?

To: current-users%NetBSD.org@localhost
Subject: Re: com(4) dialout device behavior change?
From: "John D. Baker" <jdbaker%consolidated.net@localhost>
Date: Fri, 7 Jun 2019 17:10:56 -0500 (CDT)

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

> Still need to investigate the situation regarding interrupts when using
> the "com* at acpi?" attachment.

"com* at acpi?" seems to be working again.

-- 
|/"\ 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

References:
- com(4) dialout device behavior change?
  - From: John D. Baker
- Re: com(4) dialout device behavior change?
  - From: John D. Baker
- Re: com(4) dialout device behavior change?
  - From: John D. Baker
- Re: com(4) dialout device behavior change?
  - From: John D. Baker
- Re: com(4) dialout device behavior change?
  - From: John D. Baker
- Re: com(4) dialout device behavior change?
  - From: John D. Baker

Prev by Date: sysinst garbled screen on i386 - curses issue?
Next by Date: Re: sysinst garbled screen on i386 - curses issue?
Previous by Thread: Re: com(4) dialout device behavior change?
Next by Thread: Re: com(4) dialout device behavior change?
Indexes:

Home | Main Index | Thread Index | Old Index