> Hi!
> 
> I'm working with Gigabyte H61M-S2V-B3 right now. Graphics built in CPU
> supports at most 800x600 in X.org, but the rest of the machine seems
> fine. Dmesg at dmesg@ and at NYCBUG database.
> 
> 
> Index: dev/pci/pcidevs
> ===================================================================
> RCS file: /cvs/src/sys/dev/pci/pcidevs,v
> retrieving revision 1.1618
> diff -u -p -r1.1618 pcidevs
> --- dev/pci/pcidevs   30 Aug 2011 15:57:10 -0000      1.1618
> +++ dev/pci/pcidevs   3 Sep 2011 23:04:45 -0000
> @@ -2603,10 +2603,11 @@ product INTEL QS67_LPC                0x1c4d  QS67 LPC
>  product INTEL Q67_LPC                0x1c4e  Q67 LPC
>  product INTEL QM67_LPC               0x1c4f  QM67 LPC
>  product INTEL B65_LPC                0x1c50  B65 LPC
> -product INTEL H61_LPC                0x1c51  H61 LPC
> +product INTEL 6SERIES_LPC    0x1c51  6 Series LPC
>  product INTEL C202_LPC               0x1c52  C202 LPC
>  product INTEL C204_LPC               0x1c54  C204 LPC
>  product INTEL C206_LPC               0x1c56  C206 LPC
> +product INTEL H61_LPC                0x1c5c  H61 LPC
>  product INTEL 82801AA_LPC    0x2410  82801AA LPC
>  product INTEL 82801AA_IDE    0x2411  82801AA IDE
>  product INTEL 82801AA_USB    0x2412  82801AA USB

The authoritive source for these is the Intel specification update for
the chipset.  The "old" H61 entry isn't mentioned there, so I removed
it instead of renaming it.

> Index: dev/usb/usbdevs
> ===================================================================
> RCS file: /cvs/src/sys/dev/usb/usbdevs,v
> retrieving revision 1.553
> diff -u -p -r1.553 usbdevs
> --- dev/usb/usbdevs   29 Aug 2011 10:51:18 -0000      1.553
> +++ dev/usb/usbdevs   3 Sep 2011 23:04:46 -0000
> @@ -2050,6 +2050,7 @@ product INSYSTEM ADAPTERV2      0x5701  USB St
>  
>  /* Intel products */
>  product INTEL2 RMH           0x0020  Rate Matching Hub
> +product INTEL2 RMH_SANDYBRIDGE       0x0024  Rate Matching Hub

The hub is part of the PCH rather than the CPU, so the "Sandybridge"
codename doesn't apply.  I'll see if I can come up with a better
naming scheme.

Thanks,

Mark

Reply via email to