Date: Wed, 19 Jun 2002 08:55:26 +0200 (CEST) From: Nick Hibma <n_hibma@van-laarhoven.org> To: Bruce Evans <bde@zeta.org.au> Cc: "cvs-committers@FreeBSD.org" <cvs-committers@FreeBSD.org>, "cvs-all@FreeBSD.org" <cvs-all@FreeBSD.org> Subject: Re: cvs commit: src/sys/pc98/pc98 sio.c src/sys/conf options options.i386 options.ia64 options.pc98 src/sys/dev/sio sio.c sioreg.h Message-ID: <20020619084551.E3498-100000@uitsmijter.van-laarhoven.org> In-Reply-To: <20020619153032.X7788-100000@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > This facilitates the use in circumstances where you are using a serial > > console as well. GDB doesn't support anything higher than 9600 baud (19k2 > > if you are lucky), but the console does. > > Previous version reviewed by: bde > > I seem to have missed the main point of this change. I always use gdb > at 115200 bps on i386's (since I don't have anything faster), but > haven't used it recently. Not working at a low speed like 115200 is > a bug somewhere. The buffering by the low level console driver (none) > is not very suitable for input faster than a human can type, and gdb > certainly sends input faster than tha in bursts when it sends a packet, > but problems seem to be limited by the protocol being very simple. I've had a look at the gdb code that reads the input from the port and from that I can't see why gdb would choke on reading from the port. I use a 686 class machine, so it should be well fast enough to handle the port, but anything above 19k2 gives me either spurious or permanent timeouts. Hence the change. Nick -- n_hibma@van-laarhoven.org http://www.van-laarhoven.org/ n_hibma@FreeBSD.org http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020619084551.E3498-100000>