Re: [Xen-devel] [PATCH OSSTEST v4 10/13] ts-kernel-build: Adjust kernel .config to work on the arndale boards.

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2015-01-21 at 13:20 +0000, Ian Campbell wrote:
> On Wed, 2015-01-21 at 12:05 +0000, Ian Jackson wrote:
> > Ian Campbell writes ("[PATCH OSSTEST v4 10/13] ts-kernel-build: Adjust 
> > kernel .config to work on the arndale boards."):
> > > Various drivers are missing from multi_v7_defconfig in v3.16, also
> > > some drivers which don't play nice are enabled by default, so remove
> > > them.
> > ...
> > > +# Enabling Exynos4 forces wierd CONFIG_HZ==200, and we don't
> > > +# support that platform anyway.
> > > +setopt CONFIG_ARCH_EXYNOS4 n
> > > +
> > > +# Having these on breaks USB
> > > +setopt CONFIG_SAMSUNG_USB2PHY n
> > > +setopt CONFIG_SAMSUNG_USB3PHY n
> > > +
> > > +# These cause i2c bus timeout errors on boot.
> > > +# 
> > > https://groups.google.com/a/chromium.org/forum/#!topic/chromium-os-reviews/f1DW9NcSPVU?
> > > +# http://patchwork.ozlabs.org/patch/337812/
> > > +setopt CONFIG_SENSORS_LM90 n
> > > +setopt CONFIG_ICS932S401 n
> > 
> > I think these should be gated on the kernel version and/or arch or
> > something.  After all, disabling modules is a workaround (and risks
> > making things not work in the future in an annoyingly mysterious way).
> 
> Arch I can easily do.
> 
> Not sure how easy it will be to get the kern ver,

"make kernelversion" will return the version from the Makefile (i.e. not
including any localversion stuff). The question then becomes what the
white/blacklist should look like.

Should I list all the current linux-* branch versions? How should we
handle e.g. linux-next and linux-linus?

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel