On Sun, May 04, 2008 at 01:37:47AM +0200, Krzysztof Halasa wrote:
quoted text
> Adrian Bunk <bunk@kernel.org> writes:
> 
> > FB_SGIVW requires X86_VISWS and it's selected automatically.
> >
> > (which is not good if you want a kernel that runs on a PC)
> 
> Not sure what do you mean, it currently seem to "depend" on X86_VISWS:
> 
> config FB_SGIVW
>         tristate "SGI Visual Workstation framebuffer support"
>         depends on FB && X86_VISWS
>         select FB_CFB_FILLRECT
>         select FB_CFB_COPYAREA
>         select FB_CFB_IMAGEBLIT

Unless I misunderstand your proposal you want to resolve dependencies 
reversely.

And if you want to only do this for select's: FB_SGIVW could also be 
select'ed.

quoted text
> > Why do we have to bother users with the MII option at all?
> >
> > "E1000E=m and TULIP=m but MII=y" works, but it doesn't really make 
> > sense.
> 
> (Obviously it assumes both TULIP and E1000E required MII which is not
> exactly the case)
> 
> But it makes a perfect sense, I can have modular drivers for (few)
> hardware devices (just in case I want to rmmod etc) but most of the
> kernel may be not modular. It would be nice if the Kconfig ask me if
> I want to "select" the dependency Y or M, even if there is only one
> way to make "select" dependencies happy (not counting "Y vs "M").

Getting the cases that really matter working would already be hard 
enough...

quoted text
> Krzysztof Halasa

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/