Re: hyperCOM1 and whippet fixes

[Alan B. <al...@ms...>]

hi,

> Yes Alan, I think it would be very nice if you could build the latest 2.2 CVS
> (with pending patches applied as well) on a regular basis for the test module.

this I will do. 

i was thinking....now 2.3 'works', should I also make a 2.3 test kernel
for the masses to use?
 
> - Please put the files into a subdirectory which is named like the archives

..could you explain?
 
> For the config:

thanks for the .config tips - I've been collecting 'wants and needs' from
people who have booted up and found no support for their required pieces -
and you also alerted me to 3 oversights (i cant believe it, but yes, silly
things did slip through - I'll be updating the 'standard 2.2.10' as well -
especially as HFS is needed to be in the kernel for people to install
LinuxPPC 2000  - i need a LinuxPPC 2k CD to test this out the new
installer when it arrives (soon!) myself)

> - Don't set CONFIG_MODVERSIONS. As you have noticed, it causes problems for us
>   and isn't needed anyway as we're stuck with 2.2.10 ;)

:-)  btw, is there any chance of us seeing .16 ? what issues are there
with the later 2.2.11/16 yada range?
 
> - Set CONFIG_SOUND_OSS and CONFIG_SOUND_SOFTOSS (it's a software synthesizer
>   for MIDI stuff)

okay
 
> - Finally, set CONFIG_MAGIC_SYSRQ

..now that it can compile and work :-)
 
> I leave to you what you build into the kernel and what as modules. In general,
> Stuff which isn't needed at boot time (before modules can be loaded) should be
> a module so the kernel isn't bloated too much.

as a general rule, local services that are needed to get the machien to
boot and install etc i compile in. 'Exotics' and things that you use once
you are booted (sound, serial, joystick, parallel) I try to make as
modules. After all, it has been known for the device type and
rootfilesystem type to be compiled as modules...ouch!  ;-)

alan