From owner-freebsd-current@FreeBSD.ORG  Fri Mar 12 13:10:41 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0BFF016A4D0
	for <current@freebsd.org>; Fri, 12 Mar 2004 13:10:41 -0800 (PST)
Received: from postal3.es.net (postal3.es.net [198.128.3.207])
	by mx1.FreeBSD.org (Postfix) with ESMTP id EB85E43D2D
	for <current@freebsd.org>; Fri, 12 Mar 2004 13:10:40 -0800 (PST)
	(envelope-from oberman@es.net)
Received: from ptavv.es.net ([198.128.4.29])
        by postal3.es.net (Postal Node 3) with ESMTP (SSL) id IBA74465;
        Fri, 12 Mar 2004 13:10:40 -0800
Received: from ptavv (localhost [127.0.0.1])
	by ptavv.es.net (Tachyon Server) with ESMTP
	id 2A7485D04; Fri, 12 Mar 2004 13:10:40 -0800 (PST)
To: anton@nikiforov.ru
In-reply-to: Your message of "Fri, 12 Mar 2004 23:47:10 +0300."
             <405221CE.8030402@nikiforov.ru> 
Date: Fri, 12 Mar 2004 13:10:40 -0800
From: "Kevin Oberman" <oberman@es.net>
Message-Id: <20040312211040.2A7485D04@ptavv.es.net>
cc: current@freebsd.org
Subject: Re: ATAPICAM problem 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Mar 2004 21:10:41 -0000

> Date: Fri, 12 Mar 2004 23:47:10 +0300
> From: Anton Nikiforov <anton@nikiforov.ru>
> Sender: owner-freebsd-current@freebsd.org
> 
> Looks like i have found a problem.
> When i disable hints file in the kernel config - everything become fine 
> and i can now see my cd0 perfectly :)
> Thanks everybody.

Ahh. Normally I would not recommend compiling hints into the kernel. The
main value of device hints is to allow them to be easily manipulated.

I'm sure that it marginally slows the boot operation, but it's way too
easy to have something in hints that you would like to change, but, with
hints in the kernel, you need to rebuild the kernel to make that change.

I am curious why this broke atapicam, though. Did you have something
odd in the compiled hints? Were you using the hints file in
/boot/device.hints or GENERIC.hints?
-- 
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net			Phone: +1 510 486-8634