Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 07 Aug 2006 22:25:15 +0200
From:      Thomas Wintergerst <Thomas.Wintergerst@nord-com.net>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Hellmuth Michaelis <hm@kts.org>, cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, Thomas Wintergerst <twinterg@FreeBSD.org>
Subject:   Re: cvs commit: src UPDATING src/sys/i386/include i4b_ioctl.h    src/sys/i4b/layer4 i4b_l4mgmt.c src/usr.sbin/i4b/isdnd controller.c
Message-ID:  <44D7A1AB.5070205@nord-com.net>
In-Reply-To: <20060806201649.G83232@fledge.watson.org>
References:  <200608061903.k76J3RM8008595@repoman.freebsd.org> <20060806201649.G83232@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello Robert,

Robert Watson wrote:
> On Sun, 6 Aug 2006, Thomas Wintergerst wrote:
> 
>> twinterg    2006-08-06 19:03:27 UTC
>>
>>  FreeBSD src repository
>>
>>  Modified files:        (Branch: RELENG_6)
>>    .                    UPDATING
>>    sys/i386/include     i4b_ioctl.h
>>    sys/i4b/layer4       i4b_l4mgmt.c
>>    usr.sbin/i4b/isdnd   controller.c
>>  Log:
>>  MFC:
>>
>>  Extend i4b to support CAPI manager based ISDN controllers (CAPI
>> manager is
>>  part of c4b, CAPI for BSD). This may be a preparation to add CAPI for
>> BSD to
>>  the source tree, in case the decision to MFC c4b itself is positive.
>> Until
>>  then users of c4b at least do not need to build a new kernel or base
>> system
>>  to compile and run c4b.
> 
> Any chance we will see the following change in 7.x in the near future? 
> Per discussion on arch@, the goal is to remove as many non-MPSAFEty
> crutches from the tree as possible before 7.0:

Unfortunately two things come together: I do not always have enough
time, and communication with Hellmuth, my mentor, is also a little bit
tough. Currently I am waiting for an answer to my proposal to make the
next, real integration step for c4b.

> 
> peppercorn:~/freebsd/commit/src/sys/i4b> grep -ri giant .
> ./driver/i4b_ctl.c:     .d_flags =      D_NEEDGIANT,
> ./driver/i4b_ipr.c:NET_NEEDS_GIANT("i4b_ipr");
> ./driver/i4b_isppp.c:NET_NEEDS_GIANT("i4b_isppp");
> ./driver/i4b_rbch.c:    .d_flags =      D_NEEDGIANT,
> ./driver/i4b_tel.c:     .d_flags =      D_NEEDGIANT,
> ./driver/i4b_trace.c:   .d_flags =      D_NEEDGIANT,
> ./layer4/i4b_i4bdrv.c:  .d_flags =      D_NEEDGIANT,

Regarding these sources my far goal is to let all i4b parts base on CAPI
and the CAPI manager. But this requires to transform the D-channel
sources stack to fit as a driver under the CAPI manager. A CAPI layer
module is already available. But the passive D-channel stack will take
some time, if no one helps. As of other inquiries my current work is to
implement drivers for Eicon DIVA Server ISDN boards, besides integration
of c4b into the source tree.

> 
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
> 

-- 

Gruss,

Thomas Wintergerst




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44D7A1AB.5070205>