Re: CPU_UCODE not working in a custom kernel

[Paul Goyette <paul%whooppee.com@localhost>]

On Fri, 13 Jan 2012, Paul Goyette wrote:

> I've got a custom kernel with most everything stripped out.  It built fine 
> yesterday, but today, after adding "options CPU_UCODE" it fails to build.
>
> It appears that the file firmload.c is not being included in the build, 
> probably because my stripped down kernel does not include any of the devices 
> that would drag in firmload.c (a quick check shows that the list of drivers 
> would be ral and bwi).

The following patch seems to make this work again.  Should I commit it?

diff -u -p -r1.1034 files
--- files       19 Dec 2011 16:10:07 -0000      1.1034
+++ files       14 Jan 2012 01:48:41 -0000
@@ -1427,7 +1427,7 @@ file      dev/dkwedge/dk.c
 file   dev/dkwedge/dkwedge_bsdlabel.c  dkwedge_method_bsdlabel
 file   dev/dkwedge/dkwedge_gpt.c       dkwedge_method_gpt
 file   dev/dkwedge/dkwedge_mbr.c       dkwedge_method_mbr
-file   dev/firmload.c                  firmload
+file   dev/firmload.c                  firmload | cpu_ucode
 file   dev/fss.c                       fss
 file   dev/keylock.c                   keylock
 file   dev/lockstat.c                  lockstat                needs-flag



-------------------------------------------------------------------------
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:       |
| Customer Service | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com    |
| Network Engineer | 0786 F758 55DE 53BA 7731 | pgoyette at juniper.net |
| Kernel Developer |                          | pgoyette at netbsd.org  |
-------------------------------------------------------------------------