Date: Sun, 25 May 1997 18:52:57 -0400 From: "Donald J. Maddox" <root@cola52.scsn.net> To: Wolfgang Helbig <helbig@MX.BA-Stuttgart.De> Cc: FreeBSD-current@FreeBSD.org Subject: Re: sio1: 64 events for device with no tp Message-ID: <19970525185257.34858@cola52.scsn.net> In-Reply-To: <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de>; from Wolfgang Helbig on Mon, May 26, 1997 at 12:45:59AM %2B0200 References: <19970525161640.02033@cola47.scsn.net> <199705252245.AAA00220@helbig.informatik.ba-stuttgart.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 26, 1997 at 12:45:59AM +0200, Wolfgang Helbig wrote:
> > On Sun, May 25, 1997 at 09:51:22PM +0200, Wolfgang Helbig wrote:
> > > Hi,
> > >
> > > The above kernel message shows up during booting for both sio0 and sio1.
> > > Up to now its just annoying -- the messages are repeated once
> > > syslogd is started.
> > >
> > > This behaviour seems buggy to me. These messages were not
> > > by the release 1.164 sio driver. The kernel is pretty current,
> > > using release 1.169 of sio.c. (FreeBSD-current)
> > >
> > > Only the serial interface 0 is used on this system, connected to
> > > a mouse. It still works.
> > >
> > > Maybe there is some bug in sio.c to be fixed ?
> >
> > The following is a patch from phk that will stop the messages... If you
> > want to enable the COM_BIGFIFO stuff, set FLAGS=0x20000 in the sio lines in
> > your config file (COM_BIGFIFO doesn't work for my Motorola ModemSurfer Modem.
> > YMMV).
>
> [patch omitted ...]
>
> Thank you! The patch works fine for me. Question: Why isn't it committed?
>
> Wolfgang
Well, you would really have to ask phk to get a meaningful answer about
that...
--
Donald J. Maddox
(dmaddox@scsn.net)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19970525185257.34858>