Date: Mon, 7 Nov 2005 11:57:20 +0100 From: Marius Strobl <marius@alchemy.franken.de> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/dev/puc puc.c Message-ID: <20051107115720.E65849@newtrinity.zeist.de> In-Reply-To: <10976.1131360293@critter.freebsd.dk>; from phk@phk.freebsd.dk on Mon, Nov 07, 2005 at 11:44:53AM %2B0100 References: <20051107114332.D65849@newtrinity.zeist.de> <10976.1131360293@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 07, 2005 at 11:44:53AM +0100, Poul-Henning Kamp wrote: > > In message <20051107114332.D65849@newtrinity.zeist.de>, Marius Strobl writes: > > > >On Sat, Nov 05, 2005 at 11:42:53PM +0100, Poul-Henning Kamp wrote: > >> > >> In message <20051105232325.A41277@newtrinity.zeist.de>, Marius Strobl writes: > >> > >> >PUC_FASTINTR used to cause problems on sparc64 [...] > >> >[...] I'm unsure about the > >> >details, e.g. the endless loop might actually occur a bit later > >> >during probing uart1 or before it's fully attached but I think > >> >the problem is still there. > >> > >> If so we should obviously take PUC_FASTINTR out on sparc64. > >> > > > >Well, unless you are up to fixing the problem, yes. I just gave > >it a try, when using PUC_FASTINTR the loop still occurs during > >attaching the first channel of a SAB 82532, it doesn't occur with > >a Z8530 however. > > Put an #ifdef in there then. > Wouldn't the approach jhb@ suggested, moving PUC_FASTINTR to DEFAULTS (except for sparc64) so people can easily turn it off via nooptions, be better? Bde@ indicated that the problem isn't unique to SCCs but can also happen with other devices supported by puc(4). Marius -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051107115720.E65849>