public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>
To: debian-68k@lists.debian.org
Cc: linux-m68k@vger.kernel.org
Subject: Re: Atari TT
Date: Thu, 24 Jan 2013 21:20:50 +0100	[thread overview]
Message-ID: <20130124202050.GA28593@mail.biophys.uni-duesseldorf.de> (raw)
In-Reply-To: <Pine.BSM.4.64L.1301241946080.6423@herc.mirbsd.org>

Thorsten,

> >Does the other kernel show any boot progress on the screen at all, after the
> >bootstrap has finished loading and passed control to the kernel? 
> 
> Coloured pixels.

If the other kernel (nonet) shows a proper boot screen, that's a kernel size
issue. 

On the other hand: 

> 
> >Can you send me the contents of arch/m68k/atari/config.c and
> >arch/m68k/atari/atariints.c from the patched source tree you used for these
> >kernels? 
> 
> Sure:

That does not include my more recent patches to the interrupt code. I
suspect you may be using the atari_ethernec driver instead of the generic ne
one as well. I'll check your kernel image to see what it does use. 

The ne.c network driver does not appear to tolerate interrupts arriving before 
the device has been configured, at least in the early boot phases. I'm uncertain
whether it would work even with my latest patches applied - maybe I can find
some time on the weekend to test that. 

Geert: is there some way for kernel network drivers to figure out whether the
network subsystem has been initialized, and hold off interrupt processing
before that time? I'm using 'if (netif_running(dev))' in atari_ethernec but
that does not appear to prevent the lockup. 

Cheers,

	Michael
 

       reply	other threads:[~2013-01-24 20:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20130120205231.GC32291@mail.biophys.uni-duesseldorf.de>
     [not found] ` <Pine.BSM.4.64L.1301202117270.27441@herc.mirbsd.org>
     [not found]   ` <20130120225718.GA1459@mail.biophys.uni-duesseldorf.de>
     [not found]     ` <Pine.BSM.4.64L.1301232011550.14843@herc.mirbsd.org>
     [not found]       ` <20130123212251.GA14282@mail.biophys.uni-duesseldorf.de>
     [not found]         ` <Pine.BSM.4.64L.1301232213380.14843@herc.mirbsd.org>
     [not found]           ` <20130124000856.GA15759@mail.biophys.uni-duesseldorf.de>
     [not found]             ` <Pine.BSM.4.64L.1301241759530.6423@herc.mirbsd.org>
     [not found]               ` <20130124185341.GA27701@mail.biophys.uni-duesseldorf.de>
     [not found]                 ` <Pine.BSM.4.64L.1301241946080.6423@herc.mirbsd.org>
2013-01-24 20:20                   ` Michael Schmitz [this message]
2013-01-24 20:41                     ` Atari TT Geert Uytterhoeven
2013-01-24 21:48                       ` Michael Schmitz
2013-01-25  7:30                         ` Geert Uytterhoeven
2013-01-25  8:14                           ` Michael Schmitz
2013-01-24 20:50                     ` Thorsten Glaser
2013-01-25  7:33                       ` Geert Uytterhoeven
     [not found] <4F0488A9.5030100@fairlite.co.uk>
     [not found] ` <Pine.BSM.4.64L.1201041911580.19192@herc.mirbsd.org>
     [not found]   ` <alpine.LNX.2.00.1201052128060.6601@nippy.intranet>
     [not found]     ` <4F059460.5040305@fairlite.co.uk>
     [not found]       ` <CAMuHMdUxQq_29g7yeaS2Ktz193CcHNX5FaP8PR9ijU0htnKbZg@mail.gmail.com>
     [not found]         ` <4F059AE1.6070707@fairlite.co.uk>
     [not found]           ` <4F059DB9.1050209@fairlite.co.uk>
2012-01-05 14:42             ` Geert Uytterhoeven
2012-01-05 15:49               ` Andreas Schwab
2012-01-05 19:40                 ` Alan Hourihane
2012-01-05 23:35                   ` Andreas Schwab
2012-01-05 17:04               ` Alan Hourihane
2012-01-05 19:02               ` Alan Hourihane
2012-01-05 20:35                 ` Geert Uytterhoeven
2013-01-20 16:52                   ` Thorsten Glaser

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=20130124202050.GA28593@mail.biophys.uni-duesseldorf.de \
    --to=schmitz@mail.biophys.uni-duesseldorf.de \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@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