From owner-freebsd-current@freebsd.org  Mon Jan 21 07:59:15 2019
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id A82A6149B354
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon, 21 Jan 2019 07:59:15 +0000 (UTC) (envelope-from lists@opsec.eu)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 10B3473AD0
 for <freebsd-current@freebsd.org>; Mon, 21 Jan 2019 07:59:14 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.91 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1glUUC-000Nlp-6a; Mon, 21 Jan 2019 08:59:12 +0100
Date: Mon, 21 Jan 2019 08:59:12 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Warner Losh <imp@bsdimp.com>
Cc: FreeBSD Current <freebsd-current@freebsd.org>
Subject: Re: Multiport serial card Exsys EX-44388, where are the devices ?
Message-ID: <20190121075912.GA91207@home.opsec.eu>
References: <20190120183908.GC78316@home.opsec.eu>
 <201901201920.x0KJKIEL066339@pdx.rh.CN85.dnsmgr.net>
 <20190120205811.GA1258@fc.opsec.eu>
 <CANCZdfoBpt5vjzAfazX7ezLhEYRQfhEK5xPHGM3_SYy_QctUOw@mail.gmail.com>
 <CANCZdfrVJthJGEedCNZ-nnt88Mi1xD-0HFaJXKpFGVyuPSvVhA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CANCZdfrVJthJGEedCNZ-nnt88Mi1xD-0HFaJXKpFGVyuPSvVhA@mail.gmail.com>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jan 2019 07:59:15 -0000

Hi!

> >> > Well no longer needed as puc0 has found and allocated the
> >> > device(s) which would of shown up had you done this before
> >> > you fixed puc0 to find them.

> >> The problem is that the found 4 uarts are not 8 uarts, and they do not
> >> seem to work (tested using kermit), either 8-(

> >> Any hints on how to debug this ?

> > You need to look to get the register width right.

> Hit send too quick... I was going to say you needed to make sure that the
> register width and strides were right, but they look to be because NetBSD
> has
[...]
> for this card. so there's 4 UARTs per bar, like you are seeing. You have
> DEFAULT_RCLK * 8. COM_FREQ in NetBSD is defined:
> sys/dev/ic/comreg.h:#define COM_FREQ 1843200 /* 16-bit baud rate divisor */

Ok, I modified it and rebooted. The behaviour is still the same. I'll retest
more thoroghly in the next 48 hours.

Any idea why uart(4) finds 4 without the puc modification and why it
detects 8 uarts with 16750 with the modification ?

-- 
pi@opsec.eu            +49 171 3101372                    One year to go !