I just got caught up (for an hour) on the D3D_DRIVER_TYPE_UNKNOWN argument for D3D11CreateDevice.  I guess I should have read the notes at the bottom of the SDK page.  If I pass the IDXGIAdapter interface to that function, along with D3D_DRIVER_TYPE_UNKNOWN, I can be sure that an actual HAL device has been created for that adapter, and D3D hasn't simply backpedaled to WARP or REF?

If I want to figure out which feature level an adapter supports in hardware, do I have to just try calling D3D11CreateDevice on it (and possibly not passing out pointers for device and context), and checking the returned feature level?  I was looking through the DXUT code, and it appears broken in this respect.  CD3D11Enumeration::EnumerateDevices is called on every adapter returned from IDXGIFactory1::EnumAdapters, but that IDXGIAdapter handle is never actually used, since D3D11CreateDevice passes NULL for the adapter handle.  Does DXUT11 even support multiple adapters at this point?  Looks like it wants to, but the operative statements were commented out:
        //if( devTypeArray[iDeviceType] == D3D_DRIVER_TYPE_HARDWARE )
        //    pAdapter = pAdapterInfo->m_pAdapter;

Maybe just a point for clarification in the next SDK.. 

Thanks,
.sean