Date: Wed, 10 May 2000 21:39:12 +0200 (CEST) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: "Koster, K.J." <K.J.Koster@kpn.com>, "'FreeBSD Alpha mailing list'" <freebsd-alpha@FreeBSD.ORG> Subject: Re: sio, nrc and sym questions for NoName Message-ID: <Pine.LNX.4.10.10005102026170.1255-100000@linux.local> In-Reply-To: <20000510084529.A91343@dragon.nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I will reply to this one. :) On Wed, 10 May 2000, David O'Brien wrote: > On Wed, May 10, 2000 at 04:55:50PM +0100, Koster, K.J. wrote: > > > What is the date of your kernel? The `sym' maintainer just=20 > > > added suport for the NCR 810 chip. =20 > > > > > Dunno the date, but it's the 4.0 Release iso image from ftp.FreeBSD.org= =2E > > With only 16Mb RAM I'm not going to build the world anytime soon. >=20 > Ah. The `sym' 810 support was just added, so it is not in 4.0. > =20 >=20 > > > I use the `ncr' driver on my AS 250 and have no problems with=20 > > > it. So it isn't like using `ncr' is a terriable thing. IMHO the What I can understand from the source let me think that the `ncr' has no obvious software bugs. The driver is probably quite reliable with legacy NCR 810, 815, 825. For some recent SYMBIOS chip types of early revisions, the `ncr' driver may trigger some chip errata that could not be known by the maintainers of this driver. I could carefully examine the code, compare against the errata listings I have and add 'on paper' and untested fixes, but this would just be time wasted for me given the `sym'. Btw, the `sym' learnt a lot from `ncr', as you can read in the header of each `sym' driver source files. > > > comments beside `ncr' and `sym' in the GENERIC kernel > > > configuration file tell this. > > > > Oh? It was my understanding that the ncr driver was to be replaced by t= he > > sym driver at some point. I guess that's a while off then. >=20 > I never thought it was supose to for legacy devices. But then Gerald > surprised me by adding 810(non A) and 825(non A) support to `sym'. Hmmm... I am still able to change my mind at any time and I am proud of that. :-) The short term plan for `sym' looks like: - Current sym-1.5.3 MFCed to both RELENG_4 and RELENG_3. - MFC to RELENG_4 should normally happen over the week-end. My major project about `sym' for this year is to reduce time spent for drivers maintainance and also make this driver really portable. Support for legacy NCR chips was part of this project, since it will allow me to mostly have a single driver (modulo about 1000-1500 lines of code per O/S) to maintain for all the targetted O/Ses (At least Linux and FreeBSD, obviously). G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.10.10005102026170.1255-100000>