Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Aug 2000 14:45:23 -0600
From:      Warner Losh <imp@village.org>
To:        Mike Meyer <mwm@mired.org>
Cc:        Maxim Sobolev <sobomax@FreeBSD.ORG>, Donn Miller <dmmiller@cvzoom.net>, Brooks Davis <brooks@one-eyed-alien.net>, current@FreeBSD.ORG
Subject:   Re: hints static wiring 
Message-ID:  <200008282045.OAA04141@harmony.village.org>
In-Reply-To: Your message of "Mon, 28 Aug 2000 07:54:21 CDT." <14762.24829.363032.115605@guru.mired.org> 
References:  <14762.24829.363032.115605@guru.mired.org>  <867l92lw8e.wl@tkc.att.ne.jp> <20000827184037.A22500@Odin.AC.HMC.Edu> <14762.8323.382969.782508@guru.mired.org> <39AA3882.914FC0A0@cvzoom.net> <14762.14890.276820.183791@guru.mired.org> <39AA5DC6.8D73081B@FreeBSD.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <14762.24829.363032.115605@guru.mired.org> Mike Meyer writes:
: Maxim Sobolev writes:
: > Mike Meyer wrote:
: > 
: > > Donn Miller writes:
: > > > Mike Meyer wrote:
: > > > > I do read cvs-all, and I missed it. Not did I find device.hints in the
: > > > > relevant Makefiles. Can you provide a pointer to details on how
: > > > > /boot/device.hints is used in the build process, or how having an
: > > > > empty one keeps you from shooting yourself in the foot?
: > > > Actually, device.hints isn't used in the build process.
: > > In that case, why does the kernel build process fail if it doesn't
: > > exist?
: > Probably because you have `hints "BLABLA.hints"' line in your kernel config
: > file.
: 
: That doesn't really answer the question. Yup, I use
: GENERIC.hints. That exists. I can see why that not existing would
: cause problems, but not /boot/device.hints? *Especially* when I'm
: building a kernel for a different machine?

The build of the kernel isn't forbidden by not having
/boot/device.hints, just the install.  I just copied my GENERIC.hints
to /boot/device.hints and things were happy.

: That's clearly not true - I just removed an empty /boot/device.hints
: and rebooted, and all those things work fine. I can believe that such
: things won't work if they aren't specified in some hints file, but an
: empty /boot/device.hints doesn't do anything more to specify them than
: one that isn't there.

Specifically, the console will not work without hints.  These hints
can be compiled in or in /boot/device.hints.  You need to have

hint.atkbdc.0.at="isa"
hint.atkbdc.0.port="0x060"
hint.atkbd.0.at="atkbdc"
hint.atkbd.0.irq="1"
hint.atkbd.0.flags="0x1"
hint.vga.0.at="isa"
hint.sc.0.at="isa"
hint.sc.0.flags="0x100"

At a minimum, but I might be mistaken about that.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




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