linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: Late Broadcom link detection makes IP config (bootp) fail
Date: Mon, 22 Oct 2001 12:31:12 +0800	[thread overview]
Message-ID: <3BD3A110.40703@metaparadigm.com> (raw)
In-Reply-To: 20011021202843.B4933@cpe-24-221-152-185.az.sprintbbd.net


Tom Rini wrote:

> On Mon, Oct 22, 2001 at 11:24:22AM +0800, Michael Clark wrote:
[snip]
>>Okay, changed to BMAC and it works okay - should BMAC detection come
>>before GMAC?
>>
>
> Er, say again?  And ignore what I just sent out (got confused fer a
> second).


It seems that GMAC and BMAC support some common hardware. What I was
suggesting is whether BMAC should be linked earlier so it's init
function runs before GMAC. Although I release this is not necessarily a
real solution for what may be a bug in GMAC (just means I and up using
BMAC which works and allows me to have both compiled in).

Some of GMAC initialisation seems to be delayed and done asynchronously.
Shouldn't link be detected and the interface brought up before return
from the init function? Otherwise it is impossible to use this driver
with IP autoconfig and NFS root.

~mc


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-10-22  4:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22  2:31 Late Broadcom link detection makes IP config (bootp) fail Michael Clark
2001-10-22  2:57 ` Tom Rini
2001-10-22  3:17   ` Michael Clark
2001-10-22  3:28     ` Tom Rini
2001-10-22  3:24   ` Michael Clark
2001-10-22  3:28     ` Tom Rini
2001-10-22  4:31       ` Michael Clark [this message]
2001-10-22 13:17         ` Benjamin Herrenschmidt
2001-10-22 13:16     ` Benjamin Herrenschmidt
2001-10-22 15:41       ` Tom Rini
2001-10-22 15:46         ` Geert Uytterhoeven
2001-10-22 16:42         ` Michael Clark

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=3BD3A110.40703@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=linuxppc-dev@lists.linuxppc.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 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).