[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: SS4000E Kernel v3.4 Config

I built a kernel zImage which is of size 2.77MB. This is too big to fit in
the FLASH space allocated for it in EM7220 Redboot fis (2MB) so although d-i
runs OK it fails on the final step of making the system bootable. Fis errors
if I try to fis create zImage after the load for the same reason.

Can anyone suggest some tricks to shrink it a bit?

Here are the steps I followed, largely based on Arnaud's advice.

Based the config on the iop32x_defconfig in ./arch/arm/configs of the Linux
3.4 distribution. Then added Arnaud's patches
http://git.rtp-net.org/?p=ss4000e.git;a=tree for F751111 in the following


f75111.patch fails with the following reject ./drivers/gpio/Kconfig.rej for
reasons unknown to me.

--- drivers/gpio/Kconfig	2012-05-29 00:48:29.000000000 +0200
+++ drivers/gpio/Kconfig	2012-05-29 00:53:01.915204251 +0200
@@ -558,4 +558,16 @@
 	  Enable support for GPIO on intel MSIC controllers found in
 	  intel MID devices
+config F75111
+	tristate "Fintec F75111 chip"
+	depends on I2C
+	depends on GPIOLIB
+	depends on LEDS_CLASS
+	help
+	  Say yes here if you need support for the Fintec F75111 GPIO/LED
+	  chip.
+	  This driver can also be built as a module.  If so, the module
+	  will be called f75111.

The added (+) lines which were not patched were added manually to the end of

The general procedure is here
crosstool-ng/ modified a bit for linux 3.4 and iop32x.

Define the arch, initial .config
$ make ARCH=arm iop32x_defconfig

Modify the arm iop32x one
$ make ARCH=arm menuconfig (or nconfig)

> Kernel Features > Use the ARM EABI to compile the kernel

Update .config with w83792, f751111 drivers
> Device Drivers
  > LED Support > LED Class Support
  > LED Support > LED Support for GPIO connected LEDs
  > GPIO Support > Fintec 751111
  > Device Drivers > Hardware Mon > Winbond w83792

Build using the crostool-ng toolset.
$ make ARCH=arm CROSS_COMPILE=arm-unknown-linux-gnueabi- all

zImage is in ./arch/arm/boot


-----Original Message-----
From: Chris Wilkinson [mailto:kinsham@verizon.net] 
Sent: Tuesday, July 31, 2012 4:06 PM
To: 'Arnaud Patard (Rtp)'
Cc: debian-arm@lists.debian.org
Subject: RE: SS4000E Kernel v3.4 Config

That's good advice. Where could I get the configuration from?


-----Original Message-----
From: Arnaud Patard (Rtp) [mailto:arnaud.patard@rtp-net.org] 
Sent: Tuesday, July 31, 2012 12:20 PM
To: Chris Wilkinson
Cc: debian-arm@lists.debian.org
Subject: Re: SS4000E Kernel v3.4 Config

"Chris Wilkinson" <kinsham@verizon.net> writes:

> Does anyone have a .config for the kernel v3.4.0 menuconfig they could
> The kernel builds Ok with tweaked Arnaud's patches
> (http://lists.debian.org/debian-arm/2012/07/msg00167.html) for the LEDs
> the ss4000e doesn't boot using the built zImage and ss4000e initrd.gz.
> I may be missing some important setting.
> Mine is here
> http://pastebin.com/0LCkY06F

# CONFIG_ARCH_IOP32X is not set

your kernel is not correctly configured. Your configuration is only good
if you want to boot your system on Qemu. You need at least to configure
your kernel for the right SoC and machine.

If you don't know exactly what to set, I would advice to use debian's
configuration for iop32x systems and enable the drivers added by my
patches. You may also have to take care about machine number stuff too
(the archive of this mailing list has probably the infos about this).


To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/877gtj6gxp.fsf@lebrac.rtp-net.org

To UNSUBSCRIBE, email to debian-arm-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
Archive: http://lists.debian.org/004201cd6f57$f960a1f0$ec21e5d0$@net

Reply to: