On Wed, May 1, 2013 at 3:33 AM, Debian Bug Tracking System <ow...@bugs.debian.org> wrote: > This is an automatic notification regarding your Bug report > which was filed against the linux-image-3.2.0-4-486 package: > > #706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being > compiled (needed for alix6f2) > > It has been closed by Ben Hutchings <b...@decadent.org.uk>. > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate message then please contact Ben Hutchings > <b...@decadent.org.uk> by > replying to this email. > > > -- > 706476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706476 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems > > > ---------- Forwarded message ---------- > From: Ben Hutchings <b...@decadent.org.uk> > To: 706476-d...@bugs.debian.org > Cc: > Date: Wed, 01 May 2013 03:31:35 +0100 > Subject: Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 > module not being compiled (needed for alix6f2) > On Tue, 2013-04-30 at 18:39 +0100, Ben Hutchings wrote: >> On Tue, Apr 30, 2013 at 05:22:56PM +0100, lkcl wrote: >> > Package: linux-image-3.2.0-4-486 >> > Severity: important >> > >> > >> > discovered from another debian bugreport that pc-engines systems can be >> > upgraded to more recent firmware and work with linux-image-3.2.0-4-486 >> > (which is great!) and also discovered that the geodewdt kernel module >> > has been compiled, which is also great (as it's missing from the 2.6.32 >> > debian kernel builds) >> > >> > however what's not so great is that the GPIO 5535 kernel driver has been >> > left out, and it is a requirement for the project. as native builds on >> > 500mhz AMD Geodes take absolutely forever it would be nice if this could >> > be corrected. kernel option is GPIO_CS5535 >> [...] >> >> That's odd, this was enabled in 3.1.0~rc4-1~experimental.1: >> >> * [i386] Enable GPIO_CS5535, MFD_CS5535, CS5535_MFGPT, >> CS5535_CLOCK_EVENT_SRC, GPIO_VX855, MFD_VX855 as modules; >> [i386/486] Enable OLPC_XO1_PM, OLPC_XO1_RTC, OLPC_XO1_SCI, OLPC_XO15_SCI >> (Closes: #639113) >> >> and is still enabled in the config files in the source package. >> There must be some new dependency that has forced it off again. I'll >> look at this later. > > It *is* still enabled, but it's built-in on the 486 flavour because > OLPC_XO1_SCI selects it.
thanks ben... investigating further: # PCI GPIO expanders: # CONFIG_GPIO_CS5535=y # CONFIG_GPIO_LANGWELL is not set CONFIG_GPIO_PCH=m CONFIG_GPIO_ML_IOH=m # CONFIG_GPIO_RDC321X is not set bizarre. so why the heck is.... i think it's changed quite a lot from 2.6.32, no major-minor numbers any more, to a generic GPIO interface which i've not yet understood/tracked down. so yes, more work to do but at least a route to investigate. thanks ben. l. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAPweEDxgqV-7N2z+Bv74Q3hOj33F=iyn+v-n9f3znyworoq...@mail.gmail.com
