Date: Fri, 8 Apr 2005 15:09:39 +0000 (UTC) From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Gary Jennejohn <garyj@jennejohn.org> Cc: Takahashi Yoshihiro <nyan@FreeBSD.org> Subject: Re: cvs commit: src/sys/i4b/layer1/isic i4b_isic.h Message-ID: <Pine.BSF.4.53.0504081502380.1942@e0-0.zab2.int.zabbadoz.net> In-Reply-To: <200504081456.j38EujTc011116@peedub.jennejohn.org> References: <200504081456.j38EujTc011116@peedub.jennejohn.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 8 Apr 2005, Gary Jennejohn wrote: Hi, > "Bjoern A. Zeeb" writes: > > On Fri, 8 Apr 2005, Takahashi Yoshihiro wrote: > > > > > nyan 2005-04-08 03:37:20 UTC > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/i4b/layer1/isic i4b_isic.h > > > Log: > > > Don't use 'i386/include' directly. > > > > > > Revision Changes Path > > > 1.5 +2 -2 src/sys/i4b/layer1/isic/i4b_isic.h > > > > I have a larger patch for i4b/** to correct these kinds of things > > so that i4b will be _buildable_ also for !i386. > > > > AFAIK i4b has never been _used_ on anything but i386, so the question > is - is it worth doing this for !i386? if one starts _the_ cleanup in i4b I think might be worth to also make it at least compileable and maybe working on !i386... bz@amd64:~> uname -a ; dmesg | grep ISDN FreeBSD amd64.int.zabbadoz.net 6.0-CURRENT FreeBSD 6.0-CURRENT #0: Sun Apr 3 16:02:15 UTC 2005 bz@amd64.int.zabbadoz.net:/local/building/src+ports/src/obj/local/building/freebsd/HEAD-x4b/sys/AMD64-20050403-01 amd64 i4btrc: 4 ISDN trace device(s) attached i4bctl: ISDN system control port attached i4b: ISDN call control device attached I am using capi4bsd which has an i4bcapimgr so I can use isdnd to log the calls for now... but it needs a compileable I4B for that. -- Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.53.0504081502380.1942>