From: Ookhoi <ookhoi@dds.nl>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pcmcia delay causes bootp not to work
Date: Fri, 26 Jan 2001 01:15:38 +0100 [thread overview]
Message-ID: <20010126011538.X21704@ookhoi.dds.nl> (raw)
In-Reply-To: <20010126000007.U21704@ookhoi.dds.nl> <Pine.LNX.4.30.0101252310370.2734-100000@imladris.demon.co.uk>
In-Reply-To: <Pine.LNX.4.30.0101252310370.2734-100000@imladris.demon.co.uk>; from dwmw2@infradead.org on Thu, Jan 25, 2001 at 11:11:09PM +0000
Hi David,
> Er... no, don't try that patch. It'll oops. Try this instead.
>
> --- drivers/pcmcia/yenta.c 2000/12/05 13:30:42 1.1.2.23
> +++ drivers/pcmcia/yenta.c 2001/01/25 23:10:35
> @@ -859,7 +859,8 @@
> socket->tq_task.data = socket;
>
> MOD_INC_USE_COUNT;
> - schedule_task(&socket->tq_task);
> + // schedule_task(&socket->tq_task);
> + yenta_open_bh(socket);
>
> return 0;
> }
Thank you. :-) Unfortunately, the bootp message "IP-Config: No network
devices available." still comes before the initialisation of the network
card, and thus the nf mount still failes. :-(
(this is with a clean untarred linux tree, edit and compile, and I
double checked the change in drivers/pcmcia/yenta.c)
Is there an other way to initialize the nic before bootp kickes in?
Ookhoi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-26 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 23:00 Ookhoi
2001-01-25 23:09 ` David Woodhouse
2001-01-25 23:11 ` David Woodhouse
2001-01-26 0:15 ` Ookhoi [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=20010126011538.X21704@ookhoi.dds.nl \
--to=ookhoi@dds.nl \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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®