[Bug 535] New: 2.6.21.1 kernel is broken

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Mon Apr 30 14:10:03 CEST 2007


http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=535

           Summary: 2.6.21.1 kernel is broken
           Product: OpenMoko
           Version: current svn head
          Platform: Neo1973
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: kernel
        AssignedTo: laforge at openmoko.org
        ReportedBy: koen at openembedded.org
                CC: buglog at lists.openmoko.org


The following things don't work:

* gsm power
* bt power
* gps power
* audio

the first 3 can be explained by the fact that no gta01_pm_*.ko files get created
during the kernel build, the audio one is most likely a broken asoc patch.

I wonder why this is the default kernel now...

koen at bitbake:/data/build/koen/OE/build/tmp/angstrom/work/fic-gta01-angstrom-linux-gnueabi/linux-gta01-2.6.21.1-moko9-r0/linux-2.6.21.1$
find . -name *gta01*
./arch/arm/common/gta01_pm_gps.c
./arch/arm/common/gta01_pm_gsm.c
./arch/arm/common/gta01_pm_bt.c
./arch/arm/common/gta01_pm_gsm.o
./arch/arm/common/.gta01_pm_gsm.o.cmd
./arch/arm/common/gta01_pm_gps.o
./arch/arm/common/.gta01_pm_gps.o.cmd
./arch/arm/common/gta01_pm_bt.o
./arch/arm/common/.gta01_pm_bt.o.cmd
./arch/arm/mach-s3c2410/mach-gta01.c
./arch/arm/mach-s3c2410/.mach-gta01.o.cmd
./arch/arm/mach-s3c2410/mach-gta01.o
./drivers/input/keyboard/gta01kbd.c
./drivers/input/keyboard/gta01kbd.o
./drivers/input/keyboard/.gta01kbd.o.cmd
./drivers/leds/leds-gta01.c
./drivers/leds/.leds-gta01.o.cmd
./drivers/leds/leds-gta01.o
./drivers/video/backlight/gta01_bl.c
./include/asm-arm/arch-s3c2410/gta01.h
./include/config/keyboard/gta01.h
./include/config/leds/gta01.h
./include/config/mach/gta01.h
koen at bitbake:/data/build/koen/OE/build/tmp/angstrom/work/fic-gta01-angstrom-linux-gnueabi/linux-gta01-2.6.21.1-moko9-r0/linux-2.6.21.1$



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the buglog mailing list