Re: 2.6.0-test1-ac1 Matrox Compile Error

[Dave Jones <davej@codemonkey.org.uk>]

On Tue, Jul 15, 2003 at 06:43:32PM +0100, James Simmons wrote:

 >    This still doesn't solve the issue with the input api. The input layer 
 > can be modular on many levels. Even if we force the input core to be built in 
 > this will not stop people from building the keyabord drivers as modules. 

That issue seems to have worked itself out now. I think someone already
munged the relevant Kconfig. It's been a while since l-k got a flood of
"I booted 2.5 and my keyboard doesn't work any more", whereas if you
look at all the "2.6test doesn't boot" bug reports of the last week,
and count how many of them were due to CONFIG_VT=n, you'll notice a much
bigger ratio.

 > Having PS/2 support always turned to Y will not also work since there are 
 > systems that use just USB. Their is a point where users will just have to 
 > read the README and follow directions. We can't make people do the right 
 > thing.
 >    Also doing this kind of thing only covers up broken framebuffer 
 > drivers. Unfortunetly its going to take me months to cleanup and make the 
 > fbdev drivers behave right. 

One bug at a time. With the CONFIG_EMBEDDED hack, yes it will 'hide'
this problem, but it'll likely be many months before embedded folks
start thinking of using 2.6 anyways.

		Dave