From owner-aic7xxx Tue Jan 20 16:02:09 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19914 for aic7xxx-outgoing; Tue, 20 Jan 1998 16:02:09 -0800 (PST) (envelope-from owner-aic7xxx) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19906 for ; Tue, 20 Jan 1998 16:02:05 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id QAA05221; Tue, 20 Jan 1998 16:59:37 -0700 (MST) Date: Tue, 20 Jan 1998 16:59:37 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199801202359.QAA05221@narnia.plutotech.com> To: Doug Ledford cc: aic7xxx@FreeBSD.org Subject: Re: new aic7xxx.c Newsgroups: pluto.freebsd.aic7xxx In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-aic7xxx@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In article you wrote: > > On 20-Jan-98 Luis.G.Silva@inesc.pt wrote: >> >>Bad news ! After recompiling the kernel with that new aic7xxx.c, it still >>does not recognize the SEEPROM. As soon as you have another patch to the >>aic7xxx.c please send me and I will test it. > > Bummer, I may have to contact Tyan about it :( It's a motherboard controller. They rarely use an SEEPROM to store configuration information. It's usually done by using the same NVRAM required to save PNP information. What you should be concentrating on is getting the probe to recognize that the chip was initialized by a BIOS and then use the left over BIOS information. -- Justin