linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@transmeta.com>
To: Peter Osterlund <petero2@telia.com>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
	David Woodhouse <dwmw2@infradead.org>
Subject: Re: Linux v2.5.40 - and a feature freeze reminder
Date: Sat, 5 Oct 2002 17:09:11 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.44.0210051659530.1587-100000@home.transmeta.com> (raw)
In-Reply-To: <m2r8f47af4.fsf@p4.localdomain>


On 6 Oct 2002, Peter Osterlund wrote:
>
> My PCMCIA network card no longer works. During boot, I see this
> message:
> 
>         ds: no socket drivers loaded
> 
> It worked in 2.5.39. Also this patch helps, although I don't
> understand why it is now needed:

The PCMCIA code does initializations in the wrong order, and
asynchronously (ie from multiple different threads). And init_pcmcia_ds()  
really depends on the actual low-level drivers having had time to
register, since the PCMCIA code never had any sane way to inform the DS 
layer that a new client driver had registered. 

Thus the delay by init_pcmcia_ds() - to give time for drivers to 
initialize. And the yenta driver needs some time.. That time apparently 
went up a bit, probably due to the tq/work changes.

The _right_ thing to do is to not have init_pcmcia_ds() depend on 
low-level drivers being initialized, but instead do that DS thing 
_early_, and then when each driver initializes it would tell the DS layer. 
But that's not how the PCMCIA code was organized..

		Linus


  reply	other threads:[~2002-10-06  0:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-01  7:32 Linux v2.5.40 - and a feature freeze reminder Linus Torvalds
2002-10-01  7:39 ` DevilKin
2002-10-01  8:00   ` jbradford
2002-10-01  8:04   ` Linus Torvalds
2002-10-01  8:23     ` Thomas Molina
2002-10-01  8:27       ` DevilKin
2002-10-01 10:28       ` Jens Axboe
2002-10-01  8:49 ` Gregoire Favre
2002-10-01 10:42 ` Alan Cox
2002-10-01 12:25 ` jlnance
2002-10-01 15:34   ` Dave Jones
2002-10-01 17:02   ` Vojtech Pavlik
2002-10-01 14:48 ` Denis Vlasenko
2002-10-01 17:29 ` Adrian Bunk
2002-10-01 17:44   ` Kai Germaschewski
2002-10-01 21:14 ` Christoph Hellwig
2002-10-01 22:51   ` Chris Wedgwood
2002-10-02  0:35   ` Linus Torvalds
2002-10-02  0:52     ` Alexander Viro
2002-10-02  3:12       ` Linus Torvalds
2002-10-02 12:11         ` Andries Brouwer
2002-10-02  6:51     ` Jens Axboe
2002-10-05 22:28 ` Peter Osterlund
2002-10-05 22:39   ` Kai Germaschewski
2002-10-05 23:06 ` Peter Osterlund
2002-10-06  0:09   ` Linus Torvalds [this message]
2002-10-08 21:56 ` Hans Reiser
     [not found] <fa.mpta6av.960ggh@ifi.uio.no>
     [not found] ` <fa.hu1gd9v.fku81p@ifi.uio.no>
2002-10-01  7:41   ` Nils O. =?ISO-8859-1?Q?Sel=E5sdal=22?= <noselasd@Utel.no>
2002-10-01 11:39 Markus Weiss
2002-10-01 16:35 ` James H. Cloos Jr.
     [not found] <96096729@toto.iv>
2002-10-01 23:06 ` Peter Chubb
2002-10-02  0:26   ` Chris Wedgwood

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=Pine.LNX.4.44.0210051659530.1587-100000@home.transmeta.com \
    --to=torvalds@transmeta.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=petero2@telia.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;
as well as URLs for NNTP newsgroup(s).