From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263161AbVG3Waj (ORCPT ); Sat, 30 Jul 2005 18:30:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263165AbVG3Wah (ORCPT ); Sat, 30 Jul 2005 18:30:37 -0400 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:58337 "EHLO amd.ucw.cz") by vger.kernel.org with ESMTP id S263161AbVG3Wag (ORCPT ); Sat, 30 Jul 2005 18:30:36 -0400 Date: Sun, 31 Jul 2005 00:30:30 +0200 From: Pavel Machek To: Richard Purdie , kernel list Subject: Re: Heads up for distro folks: PCMCIA hotplug differences (Re: -rc4: arm broken?) Message-ID: <20050730223030.GH9418@elf.ucw.cz> References: <20050730130406.GA4285@elf.ucw.cz> <1122741937.7650.27.camel@localhost.localdomain> <20050730201508.B26592@flint.arm.linux.org.uk> <20050730223628.M26592@flint.arm.linux.org.uk> <20050730214152.GE9418@elf.ucw.cz> <20050730225511.O26592@flint.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050730225511.O26592@flint.arm.linux.org.uk> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi! > > > > > > I merged -rc4 into my zaurus tree, and now zaurus will not boot. I see > > > > > > oops-like display, and it seems to be __call_usermodehelper / > > > > > > do_execve / load_script related. Anyone seen it before? > > > > > > > > > > For the record -rc4 works fine on my Zaurus c760 (which is pxa255 based > > > > > rather than sa1100). > > > > > > > > It appears to work fine on Intel Assabet. > > > > > > Let me qualify that, because it's not 100% fine due to the changes in > > > PCMCIA land. > > > > > > Since PCMCIA cards are detected and drivers bound at boot time, we no > > > longer get hotplug events to setup networking for PCMCIA network cards > > > already inserted. Consequently, if you are relying on /sbin/hotplug to > > > setup your PCMCIA network card at boot time, triggered by the cardmgr > > > startup binding the driver, it won't happen. > > > > Does that mean that if CF is inserted during bootup, it will simply > > appear as /dev/hda after bootup, without need to run cardmgr? > > Yes, which is almost a plus side. Whether you can use it to boot That's certainly a plus side, because I should be able to use pcmcia cards without setting much userland. Pavel -- if you have sharp zaurus hardware you don't need... you know my address