Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 Sep 1996 02:32:13 -0700 (PDT)
From:      "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com>
To:        rgrimes@freefall.freebsd.org (Rodney W. Grimes)
Cc:        CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org
Subject:   Re: cvs commit:  src/sys/pci pcisupport.c
Message-ID:  <199609060932.CAA12748@GndRsh.aac.dev.com>
In-Reply-To: <199609060917.CAA07110@freefall.freebsd.org> from "Rodney W. Grimes" at "Sep 6, 96 02:17:09 am"

next in thread | previous in thread | raw e-mail | index | archive | help
> rgrimes     96/09/06 02:17:09
> 
>   Branch:      sys/pci   RELENG_2_1_0
>   Modified:    sys/pci   pcisupport.c
>   Log:
>   First pass at merging minor differences between HEAD and RELENG_2_1_0,
>   this eliminates cosmetic differences and brings over the staticizing
>   of this file.
>   
>   Add detection of several Intel chips recently added to HEAD (Natoma and
>   Orion GX/KX).
>   
>   More clean up work will happen after pass 2 of merging once the files
>   are pretty much identical.  After that additional bootverbose chipset
>   register dumps will be added (Triton-II and Natoma).
>   
>   Revision  Changes    Path
>   1.13.4.4  +24 -19    src/sys/pci/pcisupport.c
> 

Looking at this file and all the #if defined (I686_CPU) cruft and the
ordering of chipsets makes me want a cleaner approach.  Also you have
to be _VERY_ carefull on what you exclude from certain CPU classes,
especially with devices other than HOST/PCI bridges (ie, a PCI/anything
bridge _can_ be used with _ANY_ cpu class.

Stephan, do you really want to be doing that in here??
-- 
Rod Grimes                                      rgrimes@gndrsh.aac.dev.com
Accurate Automation Company                 Reliable computers for FreeBSD



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199609060932.CAA12748>