svn commit: r225201 - in head/sys: amd64/conf i386/conf

[Doug Barton]

On 08/27/2011 14:04, Slawa Olhovchenkov wrote:
> On Sat, Aug 27, 2011 at 01:32:07PM -0700, Doug Barton wrote:
> 
>> On 08/27/2011 05:44, Slawa Olhovchenkov wrote:
>>> On Sat, Aug 27, 2011 at 04:45:44AM -0700, Doug Barton wrote:
>>>
>>>> On 8/27/2011 3:53 AM, Slawa Olhovchenkov wrote:
>>>>> On Sat, Aug 27, 2011 at 10:35:16AM +0200, Eric Masson wrote:
>>>>>
>>>>>> Slawa Olhovchenkov <slw at zxy.spb.ru> writes:
>>>>>>
>>>>>> Hello,
>>>>>>
>>>>>>> Yes, from FreeBSD 6.x puc.ko don't work. Only in-kernel version work.
>>>>>>
>>>>>> Nope puc.ko module can't attach drivers compiled in kernel, but if both
>>>>>> puc & uart are loaded as modules, they work fine :
>>>>>
>>>>>
>>>>>> The other way could be to ship a stripped down GENERIC kernel and load
>>>>>> modules manually or automagically (devd ?)
>>>>>> Regards
>>>>>
>>>>> May be for fist step: w/o devd, simle remove all posible from GENERIC and include all removed
>>>>> drivers in /boot/loader.conf?
>>>>
>>>> You're better off using kld_list in rc.conf for anything that doesn't
>>>> absolutely have to be loaded with the kernel.
>>>
>>> What drivers in GENERIC don't need to boot from disk or network?
>>> sound only?
>>
>> man rc.conf, search for kld_list.
> 
> Sorry for bad english.
> What drivers (from current GENERIC) don't need for network or disk
> boot and can be moved to kld_list?
> 
> I see only sound and agp.

I'm not going to do your homework for you. :) Try it and find out for
yourself. I will tell you that given that rc.d/kld runs right after the
disks are mounted means that (unless you are netbooting) you can put
just about everything that isn't directly related to mounting your disks
in kld_list. Beyond that, you just need to experiment on your own.


Good luck,

Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/