public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Finn Thain <fthain@telegraphics.com.au>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: "Christian T. Steigies" <cts@debian.org>,
	Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: 8390 drivers
Date: Sat, 23 Jul 2011 16:03:18 +1000 (EST)	[thread overview]
Message-ID: <alpine.OSX.2.00.1107231455010.193@ibook.intranet> (raw)
In-Reply-To: <4E2A42D1.4040201@gmail.com>


On Sat, 23 Jul 2011, Michael Schmitz wrote:

> Duplicate symbols should have been reported at link time (or when a 
> module is inserted, at latest).

I'm not so sure. If I change "mac8390.o" to "mac8390.o 8390.o" in 
drivers/net/Makefile, I get some compiler warnings but that's all. (I 
didn't try booting it. Also mac8390 is built-in -- apparently it doesn't 
do modular).

> > Yes, but if the NIC works with idle disk and fails with SCSI load, 
> > would you not blame the VIA driver?
> >   
> Not necessarily - there may be a driver locking out interrupts for too 
> long so the timeout happens before the interrupt gets serviced. Not very 
> likely - the timeout would have to run before the net bottom half.

If that were the kind of bug affecting Christian's machine, it seems 
unlikely that it would show up on a Mac. But I will add disk I/O to the 
stress test and report anything relevant.

> > I guess there are benefits to each approach? I assume that linking to 
> > 8390.o, though simpler, would end up slower (?)
> >   
> That, and it ends up not using net_ops in the driver at all. Obsolete 
> interface ...

hydra.c, zorro8390.c, 8390.c and 8390p.c all have have net_device_ops 
structs these days. I think everything got converted a year or so back.

Finn

      reply	other threads:[~2011-07-23  6:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 20:38 8390 drivers (was: Re: Debian kernel 2.6.38-5) Geert Uytterhoeven
2011-05-09 21:32 ` Christian T. Steigies
2011-05-10  6:52   ` Geert Uytterhoeven
2011-05-10  7:29     ` Christian T. Steigies
2011-05-23 20:44       ` Christian T. Steigies
2011-05-24 10:06         ` Finn Thain
2011-05-24 11:33           ` Finn Thain
2011-07-18  9:46         ` Finn Thain
2011-07-19 11:31           ` Finn Thain
2011-07-19 13:55             ` Finn Thain
2011-07-20  0:32               ` Michael Schmitz
2011-07-20  3:36                 ` Finn Thain
2011-07-23  3:41                   ` 8390 drivers Michael Schmitz
2011-07-23  6:03                     ` Finn Thain [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=alpine.OSX.2.00.1107231455010.193@ibook.intranet \
    --to=fthain@telegraphics.com.au \
    --cc=cts@debian.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=schmitzmic@googlemail.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