Date: Sun, 23 May 2004 17:18:48 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= ), Marius Strobl <marius@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/eeprom Makefile eeprom.8 eeprom.c ofw_options.c ofw_options.h Message-ID: <p06020409bcd6c46a4d65@[128.113.24.47]> In-Reply-To: <xzp3c5rf0gu.fsf@dwp.des.no> References: <200405221656.i4MGu50k062998@repoman.freebsd.org> <xzp3c5rf0gu.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
At 8:43 PM +0200 5/23/04, Dag-Erling Sm=F8rgrav wrote: >Marius Strobl <marius@FreeBSD.org> writes: > > The idea of eeprom(8) is that handlers can be written to add > > support for any firmware that stores such configuration in > > EEPROM or NVRAM; sort of e.g. eeprom(1M) on Solaris/x86 is > > used to turn PAE-support on and off (stored in a file then, > > not hardware). ... > >Would it make sense to teach eeprom(8) how to handle >/boot/loader.conf? "Handle", in what sense? How does /boot/loader.conf have any connection to anything PROM-ish? -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06020409bcd6c46a4d65>