From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: ralf@uni-koblenz.de, linux@cthulhu.engr.sgi.com, willmore@cig.mot.com
Subject: Re: MIPS 2.1.89 now in CVS
Date: Fri, 27 Mar 1998 00:47:57 +0100 [thread overview]
Message-ID: <19980327004757.19715@alpha.franken.de> (raw)
In-Reply-To: <m0yIMD7-000aNgC@the-village.bc.nu>; from Alan Cox on Thu, Mar 26, 1998 at 11:37:25PM +0000
On Thu, Mar 26, 1998 at 11:37:25PM +0000, Alan Cox wrote:
> > PC DMA controller it will be dead slow and a horror to implement (welcome
> > to world of 64K segments). If the board has it's own DMA engine, you need
> > documentation for it. And without DMA you will need a new driver.
>
> Can anyone working on generic 53c9x support also talk to the Linux mac folks
> who are also working on this right now.
the 53c9x mips support is a "port" of the sparc esp driver, which I did
based on work from the m68k people (fastlane, blizzard, etc.). And I also
verified that the changed esp still runs on a Sparc (at least on my SS2).
> Incidentally we'll also be wanting
> to abuse the mips sonic driver soon too 8)
So I should put fixing it higher on my todo list:-) ? It still has problems
with real network traffic. I know the reason, but didn't have time to fix
it, yet.
Thomas.
--
See, you not only have to be a good coder to create a system like Linux,
you have to be a sneaky bastard too ;-)
[Linus Torvalds in <4rikft$7g5@linux.cs.Helsinki.FI>]
next prev parent reply other threads:[~1998-03-26 23:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19980317234843.10411@uni-koblenz.de>
[not found] ` <9803242106.ZM28226@whelk>
1998-03-25 3:27 ` MIPS 2.1.89 now in CVS ralf
1998-03-26 23:04 ` Thomas Bogendoerfer
1998-03-26 23:37 ` Alan Cox
1998-03-26 23:37 ` Alan Cox
1998-03-26 23:47 ` Thomas Bogendoerfer [this message]
1998-03-27 0:08 ` Alan Cox
1998-03-27 0:08 ` Alan Cox
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=19980327004757.19715@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux@cthulhu.engr.sgi.com \
--cc=ralf@uni-koblenz.de \
--cc=willmore@cig.mot.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