Date: Mon, 07 Nov 2005 11:44:53 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Marius Strobl <marius@alchemy.franken.de> 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: <10976.1131360293@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 07 Nov 2005 11:43:32 %2B0100." <20051107114332.D65849@newtrinity.zeist.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?10976.1131360293>