From: Stelian Pop <stelian.pop@fr.alcove.com>
To: Dominik Brodowski <linux@brodo.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
rusty@rustcorp.com.au, torvalds@transmeta.com,
alan@lxorguk.ukuu.org.uk
Subject: Re: [CFT/RFC] pcmcia bus driver as an interface to pcmcia_socket class_type devices [Was: Re: pcmcia_bus_type changes cause oops...]
Date: Mon, 24 Mar 2003 23:59:26 +0100 [thread overview]
Message-ID: <20030324225926.GA30604@vitel.alcove-fr> (raw)
In-Reply-To: <20030324201428.GA6029@brodo.de>
On Mon, Mar 24, 2003 at 09:14:28PM +0100, Dominik Brodowski wrote:
> [Stelian: could you try this patch instead of the much smaller one
> sent before, please? Thanks!]
Patch works and reenables modular pcmcia to work. Thanks Dominik !
Except that those recent changes in the pcmcia broke the Red Hat (8.0)
boot scripts. Whether the problem lies in the scripts or the new
module dependencies is questionable.
The problem comes from the fact that loading ds.o would fail if
a socket driver is not already loaded. In the new kernel it just
wload sucessfuly.
As a side effect of that the interface is recognised as a wireless
one, and the pcmcia starting script finally doesn't load yenta_socket
because , as pcmcia_core is already loaded, it believes it is already
started. But as I said, the script logic is questionable.
Stelian.
--
Stelian Pop <stelian.pop@fr.alcove.com>
Alcove - http://www.alcove.com
prev parent reply other threads:[~2003-03-24 22:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 15:36 pcmcia_bus_type changes cause oops Stelian Pop
2003-03-24 16:25 ` Dominik Brodowski
2003-03-24 16:37 ` Stelian Pop
2003-03-24 17:17 ` Dominik Brodowski
2003-03-24 17:25 ` Stelian Pop
2003-03-24 20:14 ` [CFT/RFC] pcmcia bus driver as an interface to pcmcia_socket class_type devices [Was: Re: pcmcia_bus_type changes cause oops...] Dominik Brodowski
2003-03-24 22:59 ` Stelian Pop [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030324225926.GA30604@vitel.alcove-fr \
--to=stelian.pop@fr.alcove.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®