[Zaurus-devel] Fwd: [BUG] Spitz charger broken (and other sharpsl warnings)?
-- Forwarded message --
From: Russell King - ARM Linux li...@arm.linux.org.uk
Date: Sat, Feb 4, 2012 at 1:45 PM
Subject: [BUG] Spitz charger broken (and other sharpsl warnings)?
To: linux-arm-ker...@lists.infradead.org, eric miao
eric.y.m...@gmail.com, Haojian Zhuang haojian.zhu...@gmail.com
While building my test PXA configuration, it spat out these warnings.
There's three of them, the first probably does need fixing ASAP.
This one is particularly nasty:
arch/arm/mach-pxa/spitz_pm.c: In function 'spitz_charger_wakeup':
arch/arm/mach-pxa/spitz_pm.c:178: warning: left shift count = width of type
static unsigned long spitz_charger_wakeup(void)
{
unsigned long ret;
ret = (!gpio_get_value(SPITZ_GPIO_KEY_INT)
GPIO_bit(SPITZ_GPIO_KEY_INT))
| (!gpio_get_value(SPITZ_GPIO_SYNC)
GPIO_bit(SPITZ_GPIO_SYNC));
return ret;
}
If this impacts the way the charger works, it's definitely something that
needs fixing. We don't want more exploding batteries.
arch/arm/mach-pxa/sharpsl_pm.c: In function 'sharpsl_pm_pxa_read_max':
arch/arm/mach-pxa/sharpsl_pm.c:180: warning: ISO C90 forbids mixed
declarations and code
int sharpsl_pm_pxa_read_max(int channel)
{
/* Ugly, better move this function into another module */
if (machine_is_tosa())
return 0;
extern int max_read_channel(int); =
/* max accepts channels from 0-3, however,
* it is encoded from 0-7 here in the code.
*/
return max_read_channel(channel 1);
This seems to have been introduced by:
commit f16177c20c42e1bd780b35259a995f7718986dd4
Author: Eric Miao eric.m...@marvell.com
Date: Fri Aug 29 06:19:32 2008 +0800
hwmon: add max_read_channel() for use by sharpsl_pm
This is not generic, and is added here for backward compatibility.
It is made an individual commit here to make it easier for revert
once the sharpsl_pm gets generic enough.
Signed-off-by: Eric Miao eric.m...@marvell.com
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
diff --git a/arch/arm/mach-pxa/sharpsl_pm.c b/arch/arm/mach-pxa/sharpsl_pm.c
index e804ae0..9427d80 100644
--- a/arch/arm/mach-pxa/sharpsl_pm.c
+++ b/arch/arm/mach-pxa/sharpsl_pm.c
@@ -132,8 +132,17 @@ int sharpsl_pm_pxa_read_max(int channel)
if (machine_is_tosa()) // Ugly, better move this function into
another module
return 0;
+#ifdef CONFIG_SENSORS_MAX
+ extern int max_read_channel(int);
+
+ /* max accepts channels from 0-3, however,
+ * it is encoded from 0-7 here in the code.
+ */
+ return max_read_channel(channel 1);
+#else
return corgi_ssp_max_get((channel MAXCTRL_SEL_SH) |
MAXCTRL_PD0 | MAXCTRL_PD1
| MAXCTRL_SGL | MAXCTRL_UNI | MAXCTRL_STR);
+#endif
}
void sharpsl_pm_pxa_init(void)
arch/arm/mach-pxa/sharpsl_pm.c: At top level:
arch/arm/mach-pxa/sharpsl_pm.c:694: warning: 'sharpsl_fatal_check'
defined but not used
This warning has been around for a long time, since:
commit 99f329a2ba3c2d07cc90ca9309babf27ddf98bff
Author: Pavel Machek pa...@ucw.cz
Date: Sun Sep 6 07:28:40 2009 +0200
[ARM] pxa/sharpsl_pm: zaurus c3000 aka spitz: fix resume
sharpsl_pm.c code tries to read battery state very early during
resume, but those battery meters are connected on SPI and that's only
resumed way later.
Replace the check with simple checking of battery fatal signal, that
actually works at this stage.
Signed-off-by: Pavel Machek pa...@ucw.cz
Tested-by: Stanislav Brabec u...@penguin.cz
Signed-off-by: Eric Miao eric.y.m...@gmail.com
diff --git a/arch/arm/mach-pxa/sharpsl_pm.c b/arch/arm/mach-pxa/sharpsl_pm.c
index 2546c06..629e05d 100644
--- a/arch/arm/mach-pxa/sharpsl_pm.c
+++ b/arch/arm/mach-pxa/sharpsl_pm.c
@@ -678,8 +678,8 @@ static int corgi_enter_suspend(unsigned long
alarm_time, unsigned int alarm_enab
dev_dbg(sharpsl_pm.dev, User triggered wakeup in
offline charger.\n);
}
- if ((!sharpsl_pm.machinfo-read_devdata(SHARPSL_STATUS_LOCK))
|| (sharpsl_fatal_check() 0) )
- {
+ if ((!sharpsl_pm.machinfo-read_devdata(SHARPSL_STATUS_LOCK)) ||
+ (!sharpsl_pm.machinfo-read_devdata(SHARPSL_STATUS_FATAL))) {
dev_err(sharpsl_pm.dev, Fatal condition. Suspend.\n);
corgi_goto_sleep(alarm_time, alarm_enable, state);
return 1;
___
linux-arm-kernel mailing list
linux-arm-ker...@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
[Zaurus-devel] touchscreen calibration issues (again)
Hello, here we are again: touchscreen does not calibrate (and pointercal values are not totally correct). Yestarday built Angstrom images did not ship ts_* utils anymore and the two tools provided both fail: (on SL-C860) xinput_calibrator Error: no calibratable devices found. xtscal xcb_io.c:515: _XReply: Assertion '!dpi-xcb-reply_data' failed Aborted If I understand, the issue has been resumed here: http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/002502.html Origin: [PATCH] Remove xcalibrate and tslib support http://comments.gmane.org/gmane.comp.freedesktop.xorg.devel/10614 now, for Zaurus we have (zaurus.inc): PREFERRED_PROVIDER_virtual/xserver = xserver-kdrive XSERVER = xserver-kdrive-fbdev # c7x0 uses kdrive-imageon_1.2.0 PREFERRED_PROVIDER_virtual/xserver_c7x0 = xserver-kdrive-imageon XSERVER_c7x0 = xserver-kdrive-imageon # collie uses kdrive-fbdev PREFERRED_PROVIDER_virtual/xserver_collie = xserver-kdrive XSERVER_collie = xserver-kdrive-fbdev # FIXME xserver-kdrive 1.3.0.0 is still the only working version ? PREFERRED_PROVIDER_virtual/xserver_akita = xserver-kdrive-1300 XSERVER_akita = xserver-kdrive-1300-fbdev # spitz uses xserver-xorg PREFERRED_PROVIDER_virtual/xserver_spitz = xserver-xorg XSERVER_spitz = xserver-xorg xf86-video-fbdev xf86-input-keyboard xf86-input-mouse xf86-input-evdev PREFERRED_PROVIDER_virtual/libgl_spitz = mesa-dri I think it's time to concentrate on a *single* solution and debug it. Maybe xserver-xorg today? Suggestions? Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] locomo keyboard
Hi, I'm really not expert wrt keymaps (I hate that kind of things ;) but testing 2.6.39.1 on poodle I'm lead to think we have a wrong keymap. I suspect same breakage happens on collie. This happens in the kexecboot initramfs *and* in the shell, after loading keymap. Result: cannot type numbers and so on - unusable Now, I see some other devices patch the kernel default keymap during build. As it was working just fine with 2.6.2x overpatched kernels I'm wondering if we need some 'obvious' patch. Ideas? Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] latest angstrom image + linux-2.6.38.4 report
On Wed, May 18, 2011 at 12:31 AM, Andrea Adami andrea.ad...@gmail.com wrote: Well, again - snd-soc-spitz-not-autoloaded is a regression outside kernel. The old kernel with the new OE image has the same problem. (It means, that the kernel never provided correct info for udev module autoloading.) I've inspected /modules-2.6.38-r4-c7x0.tgz and the modules are there. Sadly, those do not appear in the rootfs produced by OE...in /lib/modules/2.6.38.5/sound there is only /sound/core and soundcore.ko I'll see how this is happening.. Andrea Quick update: about OpenEmbedded, somehow the package kernel-modules is not installed in console-image, opie-image, x11-image, just in x11-gpe-image! We should now decide which modules to add in zaurus.inc (i.e. MACHINE_EXTRA_RRECOMMENDS = kernel-modules for *all* compiled modules or a list). Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Zaurus poodle -no poweroff
On Mon, May 16, 2011 at 11:17 AM, Dmitry Eremin-Solenikov
dbarysh...@gmail.com wrote:
Hello,
On 5/16/11, Andrea Adami andrea.ad...@gmail.com wrote:
Hello,
I noticed hat using 2.6.3x kernel the Zaurus poodle restarts instead of
halt.
Since 2.6.26 poodle.c contains:
417 static void poodle_poweroff(void)
418 {
419 arm_machine_restart('h', NULL);
420 }
This happens even using kexecboot (LINUX_REBOOT_CMD_POWER_OFF)
Honestly I never tested poodle with older kernels so I cannot say
how/if it was working.
I've checked old (Sharp) kernel for POODLE-specific code. It seems there was
no way to turn it off.
--
With best wishes
Dmitry
Ah,
so there is no way to put the machine in it's initial state after
inserting the battery?
Just suspend/resume?
Same for collie?
Andrea
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Zaurus GPIO buttons with matrix keypad drivers
On Mon, May 2, 2011 at 2:18 PM, Andrea Adami andrea.ad...@gmail.com wrote: Hello, following comments from a Stanislav patch Spitz switched to generic matrix-gpio keyboard driver in 2.6.32-rc0, but that means that support for power button and lid switches was lost. This restores it, using button-gpio code. in the 2.6.38 source I only find in spitz.c: #if defined(CONFIG_KEYBOARD_GPIO) || defined(CONFIG_KEYBOARD_GPIO_MODULE) static struct gpio_keys_button spitz_gpio_keys[] and in tosa.c : static struct gpio_keys_button tosa_gpio_keys[] What about the rest of Zaurus? Fwiw corgi and poodle does not react at all... Any hope we'll have those GPIO-buttons back on all Zaurus models? Is it an hard patch? Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] spitz- 2.6.38 boot from CF bug
So, here the logs booting from CF, what kexecboot-kernel thinks /dev/sda[1;2] http://paste.debian.net/116047/ http://paste.debian.net/116048/ The 'production' kernel mounts internal HD first: scsi 0:0:0:0: Direct-Access ATA HMS360606D5CF00 DP6O PQ: 0 ANSI: 5 scsi 1:0:0:0: Direct-Access ATA SanDisk SDCFH-00 HDX PQ: 0 ANSI: 5 so... no init found :) Solutions? Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] spitz- 2.6.38 boot from CF bug
On Tue, May 3, 2011 at 10:48 AM, Dmitry Eremin-Solenikov dbarysh...@gmail.com wrote: On 5/3/11, Andrea Adami andrea.ad...@gmail.com wrote: Hi, I do boot spitz very seldom and lately I've seen strange failures when booting from CF card on spitz. For other Zaurus c7x0 and poodle no issues. Log of two failures is here: http://paste.debian.net/115815/ Please try booting w/o 'quiet' kernel parameter and with 'debug' parameter enabled. Sure, I'll take full logs (the first one should already be with debug). I forgot to say that I boot those kernel from kexecboot. I'm lead to think the issue is originated by the 'random' ordering done by new ATA driver, as if the comandline would point to /dev/sda1 and the target kernel thinks the device is /sdb1 FWIW kexecboot kernels boots much more rapidly, having no modules, so maybe this is a pure timing/detection issue. I'll take more verbose logs. FIW when booted from SD card the ATA peripherals are detected just fine. http://paste.debian.net/115817/ I think to remember I've read about driver bugs in 2.6.38 and I hope those are solved in 2.6.39. Will see soon. -- With best wishes Dmitry TIA Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Zaurus GPIO buttons with matrix keypad drivers
Hello, following comments from a Stanislav patch Spitz switched to generic matrix-gpio keyboard driver in 2.6.32-rc0, but that means that support for power button and lid switches was lost. This restores it, using button-gpio code. in the 2.6.38 source I only find in spitz.c: #if defined(CONFIG_KEYBOARD_GPIO) || defined(CONFIG_KEYBOARD_GPIO_MODULE) static struct gpio_keys_button spitz_gpio_keys[] and in tosa.c : static struct gpio_keys_button tosa_gpio_keys[] What about the rest of Zaurus? Fwiw corgi and poodle does not react at all... Andrea [1] ... Signed-off-by: Pavel Machek ... ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] spitz- 2.6.38 boot from CF bug
Hi, I do boot spitz very seldom and lately I've seen strange failures when booting from CF card on spitz. For other Zaurus c7x0 and poodle no issues. Log of two failures is here: http://paste.debian.net/115815/ FIW when booted from SD card the ATA peripherals are detected just fine. http://paste.debian.net/115817/ I think to remember I've read about driver bugs in 2.6.38 and I hope those are solved in 2.6.39. Will see soon. Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Event based zaurusd
Hello, now that we are running 2.6.38 kernels can we move to the new event based zaurusd [1]? Any particular drawback? Regards Andrea [1] http://metan.lindevdoc.org/git/?p=zaurusd.git/.git;a=summary ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Event based zaurusd
reading following lines from linux-arm-kernel [2] I wonder if we could have zaurusd as driver in kernel tree... ... Since this is a one-off kind of thing, a singleton driver that controls power, reset and some GPIO on the chip. I contemplate moving the stuff to either: drivers/misc/ux500/* include/linux/misc/ux500/* or: drivers/platform/arm/ux500/* include/linux/platform/arm/ux500/* Are any of these generally speaking good ideas? Or maybe drivers/arm? ... [2] http://lists.infradead.org/pipermail/linux-arm-kernel/2011-April/048211.html Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] mtd-utils - issues with flash_eraseall -j
On Thu, Mar 24, 2011 at 2:17 PM, Andrea Adami andrea.ad...@gmail.com wrote: Same failure with 2.6.38 on c7x0 / akita / spitz. Ideas? Andrea -- Forwarded message -- From: Andrea Adami andrea.ad...@gmail.com Date: Wed, Mar 9, 2011 at 10:33 AM Subject: Re: mtd-utils - issues with flash_eraseall -j To: openembedded-de...@lists.openembedded.org I have a guess: Patchwork [5/5] mtd-utils: change flash_eraseall to use libmtd-wrapped ioctls http://patchwork.ozlabs.org/patch/57934/ Then I've read that recently (1.4.x) ...The struct nand_oobinfo is able to record only 32 ECC code positions,which is not enough for many big NAND chips. Therefore, this structure is replaced by struct nand_ecclayout in linux kernel from the version 2.6.17. Consequently, the ioctl command changed from MEMGETOOBSEL to ECCGETLAYOUT I was using 2.6.26 kernel. Please report if that happens on other hardware too. Thanks Andrea On Wed, Mar 9, 2011 at 1:14 AM, Andrea Adami andrea.ad...@gmail.com wrote: Hello, with the previous mtd-utils-1.3.1 I could do ' flash_eraseall -j /dev/mtd3' on my Zaurus/armv5te. With v. 1.4.1 (and 1.4.2 fwiw) I see following errors: ... flash_erase: error!: /dev/mtd3: MTD writeoob failure error 22 (Invalid argument) Erasing 16 Kibyte @ 43f -- 99% complete libmtd: error!: unaligned address 7 1237640, mtd3 page size is 512 flash_erase: error!: /dev/mtd3: MTD writeoob failure error 22 (Invalid argument) Erasing 16 Kibyte @ 43f4000 -- 99% complete libmtd: error!: unaligned address 7 1254024, mtd3 page size is 512 ... Anybody can confirm the issue? Regards Andrea It seems the issue has been aknowledge and resolved upstream. http://lists.infradead.org/pipermail/linux-mtd/2011-April/034599.html Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Fwd: mtd-utils - issues with flash_eraseall -j
Same failure with 2.6.38 on c7x0 / akita / spitz. Ideas? Andrea -- Forwarded message -- From: Andrea Adami andrea.ad...@gmail.com Date: Wed, Mar 9, 2011 at 10:33 AM Subject: Re: mtd-utils - issues with flash_eraseall -j To: openembedded-de...@lists.openembedded.org I have a guess: Patchwork [5/5] mtd-utils: change flash_eraseall to use libmtd-wrapped ioctls http://patchwork.ozlabs.org/patch/57934/ Then I've read that recently (1.4.x) ...The struct nand_oobinfo is able to record only 32 ECC code positions,which is not enough for many big NAND chips. Therefore, this structure is replaced by struct nand_ecclayout in linux kernel from the version 2.6.17. Consequently, the ioctl command changed from MEMGETOOBSEL to ECCGETLAYOUT I was using 2.6.26 kernel. Please report if that happens on other hardware too. Thanks Andrea On Wed, Mar 9, 2011 at 1:14 AM, Andrea Adami andrea.ad...@gmail.com wrote: Hello, with the previous mtd-utils-1.3.1 I could do ' flash_eraseall -j /dev/mtd3' on my Zaurus/armv5te. With v. 1.4.1 (and 1.4.2 fwiw) I see following errors: ... flash_erase: error!: /dev/mtd3: MTD writeoob failure error 22 (Invalid argument) Erasing 16 Kibyte @ 43f -- 99% complete libmtd: error!: unaligned address 7 1237640, mtd3 page size is 512 flash_erase: error!: /dev/mtd3: MTD writeoob failure error 22 (Invalid argument) Erasing 16 Kibyte @ 43f4000 -- 99% complete libmtd: error!: unaligned address 7 1254024, mtd3 page size is 512 ... Anybody can confirm the issue? Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Zaurus: kernel 2.6.38
Hello, it seems vanilla kernel 2.6.38 boots just fine on all Zaurus models. We have fresh recipes in OpenEmbedded (linux and linux-kexecboot) for c7x0, akita, spitz, poodle. Collie and tosa will be committed later today. Test images will be uploaded soon. Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Zaurus: kernel 2.6.38
On Wed, Mar 16, 2011 at 2:25 PM, Stanislav Brabec u...@penguin.cz wrote: Andrea Adami wrote: it seems vanilla kernel 2.6.38 boots just fine on all Zaurus models. We have fresh recipes in OpenEmbedded (linux and linux-kexecboot) for c7x0, akita, spitz, poodle. Collie and tosa will be committed later today. Not only that it boots. Even battery seems to survive overnight suspend! I just seen following problems: - I guess that I seen some errors about missing audio (untested). - tslib stopped to understand /dev/input/touchscreen0. There are two issues there: using linux-rp there is a bunch of module_autoload_snd-pcm-oss = snd-pcm-oss module_autoload_pcmcia_core = pcmcia_core ... module_autoload_snd-soc-spitz_spitz = snd-soc-spitz I'd say, here we can build those modules in kernel... After fixing these two issues, it may be a good candidate for update the default kernel in the feeds. Yes, first target is moving to linux.inc and second step will be 'use standard udev'. Third step is the new event-driven zaurusd. Fourth step (to be discussed) is moving all to xorg-xserver. Opinions? And long time running issues: - Serial without console may need to close/open after suspend to work again. - Suspend still has problems with MAX (but offline charging surprisingly seems to work, I did not test whether even stopping of charging works) - Unfiltered touchscreen precision is still tragical (50 pixel jumps are not exceptions). - I still did not find to finish my resistor array keyboard driver (AKA remote control). I will probably port the old one to get remote working there. - Status of filesystem corruptions is not known (it is happening with varying frequency in all 2.6 kernels). OFC, bugs are always around but at least we'll be not alone fiddling with old kernels... Regards Andrea -- Stanislav Brabec http://www.penguin.cz/~utx/zaurus ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] tosa 2.6.36
Hallo Franck, thanks for reporting. USB has been disabled for size-reasons. Should be re-enabled with networking if possible. The linux-kexecboot-2.6.36 defconfig for tosa already has CONFIG_KEYBOARD_MATRIX=y FWIW this was left too unset # CONFIG_TOSA_USE_EXT_KEYCODES is not set i took my rootfs to create his on his cf card (/dev/hda1) Be careful: you should use the same ide driver for linux-kexecboot_tosa and for linux_tosa: being that most machines are still on older kernels I left the old deprecated ATA/IDE driver which gives /dev/hda. The best news are that Dmitry is working again on tosa-kernel! Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] [zaurus] linux-kexecboot-2.6.36-r24-new-GUI
On Tue, Nov 2, 2010 at 3:54 PM, Franck L fra...@kernlog.net wrote: hello Andrea :) kexecboot 2.6.36-rc24.0-new_gui test on sl-c3100 : borzoi 3 boot, 3 times same problem : kexecboot doesn't see the hda1 zImage on first boot. I have to rescan device, and there, it sees it. Yes, this happens if you don't have *any* image in nand. Both on spitz and on c7x0. We'll have to add more delay to allow some lazy CF cards to register or to abandon our 'device-recreating' model and just rely on devtmpfs (for the recent kernels). Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] [zaurus] linux-kexecboot-2.6.36-r24-new-GUI
Hello, I've uploaded Zaurus 2.6.36 kexecboot kernels with the new gui: http://projects.linuxtogo.org/projects/zaurus/ Please test and report, mostly interested on collie, poodle, tosa. Regards Andrea P.S. Tested on: c7x0 : boots, kexecboot is ok (power button has no effect ?) spitz: boots, kexecboot is ok, (some strange freezes, power button dims the screen) ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] kexecboot 2.6.2x-new-gui hwclock problem
Franck, Another Option would be to flash a console imgae to Nand. That's the setup I use on my poodle. That way I have a way to recover bad SD cards or other issues... Plus the Nand on a poodle is kinda small for other stuff anyways. well, that would be a great idea... Yes, like Henry said, that's what I would suggest. Even two (small) images in nand. easy with updater.sh: rename the console-image.jffs2 to initrd.bin - mtd2 or home.bin - /mtd3 but, as Yuri told me : NAND scanning takes most part of time. If you have nothing useful in NAND then just erase it with mtd-utils. and as i though that kexecboot was long to scan, i wanted to follow his advice and erase the NAND. Old broken jffs2 layout takes very long...clean with flash_eraseall -j /dev/mtd[2:3] if the kexecboot console isn't do-able , i'll do what you told me, and put a console-image on the Nand. Thank you :) Remember you can always build an uclibc console image ;) franck -- Henry von Tresckow (hvontres) Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Problem with module renaming from 2.6.28 to 2.6.29 (ieee80211 to lib80211)
I figured out one of the problems I reported to the zaurus-devel list, namely that of why wep wasn't working on a cf card with tosa. The reason was that in 2.6.29 ieee80211 changed name to lib80211, meaning that task-base-wifi the following didn't load the appropriate modules for wep. bump ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Fwd: [PATCH] [ARM] pxa/corgi: fix MMC/SD card detection failure
-- Forwarded message --
From: Eric Miao eric.y.m...@gmail.com
Date: Mon, Jun 14, 2010 at 12:19 PM
Subject: [PATCH] [ARM] pxa/corgi: fix MMC/SD card detection failure
To: linux-arm-kernel linux-arm-ker...@lists.infradead.org
Cc: Andrea Adami andrea.ad...@gmail.com, Eric Miao eric.y.m...@gmail.com
Reported-by: Andrea Adami andrea.ad...@gmail.com
Signed-off-by: Eric Miao eric.y.m...@gmail.com
---
arch/arm/mach-pxa/corgi.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-pxa/corgi.c b/arch/arm/mach-pxa/corgi.c
index 3d1dcb9..51ffa6a 100644
--- a/arch/arm/mach-pxa/corgi.c
+++ b/arch/arm/mach-pxa/corgi.c
@@ -446,7 +446,7 @@ static struct platform_device corgiled_device = {
static struct pxamci_platform_data corgi_mci_platform_data = {
.detect_delay_ms = 250,
.ocr_mask = MMC_VDD_32_33|MMC_VDD_33_34,
- .gpio_card_detect = -1,
+ .gpio_card_detect = CORGI_GPIO_nSD_DETECT,
.gpio_card_ro = CORGI_GPIO_nSD_WP,
.gpio_power = CORGI_GPIO_SD_PWR,
};
--
1.7.1.251.g92a7
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Fwd: Heads up: Linus plans to kill ARM defconfigs
I post here a single msg from the mega-thread, because even if it is rejected by Linus we could reuse it in OE :) The idea is reducing the defconfigs: for Zaurus we have very much in common between defconfigs, so much that Iwas thinking to just create the diffs. Now Eric seems having a better method... Opinions? Andrea -- Forwarded message -- From: Eric Miao eric.y.m...@gmail.com Date: Tue, Jun 8, 2010 at 4:51 PM Subject: Re: Heads up: Linus plans to kill ARM defconfigs To: Russell King - ARM Linux li...@arm.linux.org.uk Cc: Amit Kucheria amit.kuche...@canonical.com, Nicolas Pitre n...@fluxnic.net, Tony Lindgren t...@atomide.com, Martin Guy martinw...@gmail.com, Marek Vasut marek.va...@gmail.com, Ryan Mallon r...@bluewatersys.com, Andy Whitcroft a...@canonical.com, linux-arm-ker...@lists.infradead.org On Tue, Jun 8, 2010 at 9:13 PM, Russell King - ARM Linux li...@arm.linux.org.uk wrote: On Tue, Jun 08, 2010 at 09:01:35AM -0400, Nicolas Pitre wrote: I wouldn't give up on that option just yet though. I don't think he fully understood your idea, and without an actual patch it might be hard to understand as well, especially for people who are not used to deal with the target varieties we have on ARM. Linus is also known to change his mind when presented with evidences. The two ideas are very close to each other - and can be generated together. If we create something like Linus' preferred solution, we can then do in the main arch/arm/Kconfig: config STD_CONFIG bool blah if STD_CONFIG if MACH_WHATEVER include arch/arm/config/Kconfig.whatever endif if MACH_BLAH include arch/arm/config/Kconfig.blah endif endif which should work as per my idea. Anyway, we might need a tool to analyze those common config options across all boards, and those not. Attached is a script used when updating debian kernel configs, which I found might be useful. The result is still a _big_ mess to sort out though. Below is what I did: 1. Generating a complete list of configs (updated) ycm...@macbook-lucid:~/kernel/linux-2.6$ for i in arch/arm/configs/*; do j=`echo $i | sed 's/.*configs\/\(.*\)_defconfig/\1/'`; echo $j; mkdir ../build/tmp; make ARCH=arm O=../build/tmp `basename $i`; make ARCH=arm O=../build/tmp oldconfig; cp ../build/tmp/.config ../configs/config.$j; rm -fr ../build/tmp; done 2. Use splitconfigs.pl shows the reduction of config options ycm...@macbook-lucid:~/kernel/configs$ cat * | wc -l 258408 ycm...@macbook-lucid:~/kernel/configs$ splitconfig.pl . Reading config's ... Merging lists ... Creating common config ... done. Creating stub configs ... ycm...@macbook-lucid:~/kernel/configs$ cat * | wc -l 142062 3. A config.common includes those options common to all config.* and the remaining config.* now only includes those could be different across boards. ___ linux-arm-kernel mailing list linux-arm-ker...@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel splitconfig.pl Description: Binary data ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Evfilter
Evfilter is userspace library for filtering/modifying input events from linux kernel input layer, created by Cyril (metan) Hrubis. http://atrey.karlin.mff.cuni.cz/~metan/evfilter/ Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] [oe] [RFC] Zaurus: make updater.sh obsolete for poodle, clamshells and tosa
I rebump the topic because a couple of weeks ago I did some changes to zaurus-updater. The actual revision in OE has following targets (in capitals too): Part. File mtd1 uboot.bin = u-boot (deprecated - old testing) mtd1 zImage/zImage.bin = kernel mtd2 initrd.bin = rootfs (now *with or without 16b sharp-headers*) mtd3 home.bin = here you can flash a second rootfs or restore a backup of /home if set on mtdblock3 in fstab hdd1 hdimage1.tgz = rootfs on first hdd partition (spitz only. Do we really need this one and gnu-tar for the installer?) I suppose that all models where originally shipped with 'signed' binaries, to have a coherent master version. We still don't have a precise idea about the used checksum... Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Testing linux-kexecboot_2.6.34-rc4
Files have been uploaded here: http://projects.linuxtogo.org/frs/?group_id=55 Thx for testing! Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Unified EABI toolchain for Zaurus
Hello, I recently built for armv4 EABI (collie) and this pulled in gcc_4.4.2 (and binutils_2.20). I see these are the defaults in sane-toolchain.inc, however e.g. Angstrom-2008.1 doesn't include that file and so a second 4.3 gcc is built for the armv5te machines. I propose to bump the toolchain to the same version as armv4, in order to unify the toolchain for the different Zaurus machines. For the moment we could override in zaurus-2.6.inc. Opinions? Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Testing linux-kexecboot_2.6.34-rc3
Please test them: I tried to uniform the config used by Zaurus machines but tosa and collie are very different... about collie, I see an obvious problem in my defconfig: # CONFIG_MMC_SPI is not set That would mean no MMC card... I brought down the install test kit for the collie and flashed it. When I reset after the flash I get a Angstrom Logo with a white text at well, at least it boots... I'll try to fix it asap Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Sharp IS01
Still not a Zaurus, but close... http://au-is.jp/products/is01/ ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] the latest kexecboot
Hello, I released stable 2.6.26 and testing 2.6.33-rc6 here: http://projects.linuxtogo.org/projects/zaurus/ Known issues of linux-kexecboot-2.6.3x (on c7x0): - power button does not suspend - probable bug for pxa25x and MMC (hotplug of another SD card seems not sensed) Tests are welcome. Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Original 2.4 files and sources
Hello, links on this page are pointing to the (disappeared) 2.4 sources: http://tetsu.homelinux.org/zaurus/kernel/ There are the original updaters too. Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] About kernel decompressors (fwd)
OMG... we can even avoid that pxa-linking-bug-r1 patch! 2.6.33-rc6 boots vanilla. [more after LZMA testing] Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Booting LZMA kernel
Update: Moreover, 2.6.33-rc5 refuses to boot from nand, with or without patch. Seems a regression from -rc4. See: Uncompressing broken with commit e7db7b4270 http://lists.infradead.org/pipermail/linux-arm-kernel/2010-January/008792.html So, no point of adding LZMA if infrastructure is still unstable... Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] Booting LZMA kernel
Hello,
still unable to boot lzma-compressed kernel.
Same kernel boots from kexec: http://fr.pastebin.ca/1763395
2.6.33-rc5 using the patches :
ARM-Add-support-for-LZMA-compressed-kernel-images.patch;patch=1;status=pending
${RPSRC}/pxa-linking-bug-r1.patch
Any hint is appreciated :)
Regards
Andrea
P.S. I tried even LZO...same issue. No life after JUMP to LINUX!
___
Zaurus-devel mailing list
Zaurus-devel@lists.linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] bootloader params
Hello, I see on LAKML there is buzz about old_params today: [PATCH] arm: remove support for old way to pass kernel parameters http://lists.infradead.org/pipermail/linux-arm-kernel/2010-January/008032.html [PATCH] arm: deprecate support for old way to pass kernel parameters http://lists.infradead.org/pipermail/linux-arm-kernel/2010-January/008039.html Are we affected? Is it now the moment to propose some zaurus-specific hacks in kernel in order to be able to retrieve the mtdparts passed in the old way by our old-fashioned bootloader? And more, would it be possible to still pass the old_params in order to boot 2.4 / atags-unaware kernels? I think at the issue we have with kexecboot and 2.4 (cacko-sharp) kernels: these rely on a predefined mtd partitioning, being that they don't find any params at the expected (now deprecated) address. Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] Strange problem with kexec on C700
I hope we can finally sort out the issue... Low Ram could be a problem kexec, yes. But we already found-out that enabling CPU_FREQ would make kernel unbootable on C700 (e.g. no reboot after flashing with updater.sh) I'll build a 2.26 kernel with old kexec-tools and without cpu_freq to have it tested. Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] 2.6.33-rc1: good news
Hello Stanislav, Unfortunately I have a fresh report from JaMa about wrong... BTW this was on Spitz. So the question is: does the prom appear somewhere in /proc/partitions? I could not find it on say mtd3... Kernel makes no guarantee of partition order. It depends on order of evaluation. If both drivers (PROM, NAND) are in modules, it can vary even across reboots. Ok, so what to do? Patch the kernel? How do other boards with NOR and NAND do? Imho we should respect the factory layout and keep kernel in mtd1. Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] 2.6.33-rc1: good news
But this is critical problem only for boot. In the user space, there is a lot of chances to prevent it (udev, mount by ID). ... So it would not be possible. Either mtd0 or mtd2. ok, so the only issue could be with pre 2.6.30 kernels / userspaces ? With patched kexecboot I got now get : Got device '/dev/mtdblock0' (31, 0) of size 7Mb Probing /dev/mtdblock0 FS could not be identified Can't detect FS type Got device '/dev/mtdblock1' (31, 1) of size 53Mb Probing /dev/mtdblock1 + FS on device is jffs2 Got device '/dev/mtdblock2' (31, 2) of size 68Mb Probing /dev/mtdblock2 + FS on device is jffs2 Got device '/dev/mmcblk0' (179, 0) of size 489Mb Probing /dev/mmcblk0 FS could not be identified Can't detect FS type Got device '/dev/mmcblk0p1' (179, 1) of size 486Mb Probing /dev/mmcblk0p1 + FS on device is ext2 Can't read next device line Found 3 items + processing 0: angstrom + processing 1: angstrom + processing 2: angstrom * maximum priority 0 found at 0 + [angstrom /dev/mtdblock1 jffs2 53Mb] + processing 1: angstrom + processing 2: angstrom * maximum priority 0 found at 1 + [angstrom /dev/mtdblock2 jffs2 68Mb] + processing 2: angstrom * maximum priority 0 found at 2 + [angstrom /dev/mmcblk0p1 ext2 486Mb] load_argv: /usr/sbin/kexec, -l, --command-line=root=/dev/mtdblock2 rootfstype=jffs2 rootwait console=ttyS0,115200n8 console=tty1 noinitrd debug, /mnt/boot/zImage No network is detected, disabling ifdown() exec_argv: /usr/sbin/kexec, -e, -x Uncompressing Linux... What will happen booting a 2.6.26 kernel? In fstab we have: rootfs / autodefaults1 1 How will be translated mtdblock2 (31, 2) of size 68Mb ? Finally, I'd like to fix the recipes of kexecboot and nandlogical in order to respect the new layout. Perhaps with some version-checking logic? Happily updater.sh relying on 2nd 2.4 kernel still works vanilla. Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
Re: [Zaurus-devel] 2.6.33-rc1: good news
Hello, still lacking the rom partition in mtd0. Partitions count is wrong (kernel in mtd0). I would hope the corgi OOB/BBT are ok... And about MMC, I suppose I'm doing something wrong because if I exchange the SD card and reScan the kexecboot menu removes the old entries but doesn't list the new ones (are not yet in /proc/partitions ?) Strangely I had report that on spitz these two issues are unknown! I updated the kernel config for spitz/akita with minor edits of c7x0 defconfig: if this one is fine on c3xxx (the rom is listed in mtd0 and SD cards are detected on rescan), then it would be a corgi specific problem. http://cgit.openembedded.org/cgit.cgi/openembedded/tree/recipes/kexecboot/linux-kexecboot-2.6.32+2.6.33-rc3 Thanks in advance for testing Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
[Zaurus-devel] corgi_ts
Hello, trying to take care of the bugreports of OpenEmbedded referred to zaurus kernels ( http://tinyurl.com/yde4qxc ) I found the #2636 interesting. Now, corgi_ts has been deprecated but I'm unsure all old issues have been solved. See http://markmail.org/message/wvms4qxmfovhai53. IIRC some work has been done in order to filter the spurious events. Anyone can comment on the actual status? Regards Andrea ___ Zaurus-devel mailing list Zaurus-devel@lists.linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/zaurus-devel
