From: Stelian Pop <stelian@popies.net>
To: Tom Rini <trini@kernel.crashing.org>
Cc: kgdb-bugreport@lists.sourceforge.net,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Amit S. Kale" <amitkale@emsyssoft.com>,
ganzinger@mvista.com
Subject: Re: [Kgdb-bugreport] [KGDB] Make kgdb get in sync with it's I/O drivers for the breakpoint
Date: Tue, 6 Apr 2004 17:30:13 +0200 [thread overview]
Message-ID: <20040406153013.GS2718@deep-space-9.dsnet> (raw)
In-Reply-To: <20040406145741.GX31152@smtp.west.cox.net>
On Tue, Apr 06, 2004 at 07:57:41AM -0700, Tom Rini wrote:
> > Maybe this could be done in a more kgdb-independent way in the
> > netpoll layer. There is already some code there who waits for
> > the carrier on a net card. Maybe this could be extended to also
> > wait for the network card to appear...
>
> I was thinking about that as well. But what I'm guessing happens now is
> that netpoll_setup(&np) fails causing us init_kgdboe to fail.
Yup.
> If we're
> going to queue up the signal and wait for an eth0, what would it return
> to let us known it'll be ready 'someday' ?
What about adding a
void (*netpoll_up)(struct netpoll *)
callback into the netpoll struct ?
Using this, netpoll_setup() would return immediately, doing its job
in background, and will signal the caller using the 'netpoll_up'
function when the card is ready to go...
Stelian.
--
Stelian Pop <stelian@popies.net>
next prev parent reply other threads:[~2004-04-06 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 23:30 [KGDB] Make kgdb get in sync with it's I/O drivers for the breakpoint Tom Rini
2004-04-06 14:51 ` [Kgdb-bugreport] " Stelian Pop
2004-04-06 14:57 ` Tom Rini
2004-04-06 15:30 ` Stelian Pop [this message]
2004-04-06 20:58 ` George Anzinger
2004-04-06 21:04 ` Tom Rini
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=20040406153013.GS2718@deep-space-9.dsnet \
--to=stelian@popies.net \
--cc=amitkale@emsyssoft.com \
--cc=ganzinger@mvista.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.