From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: iop_msg_pool
Date: Mon, 1 Jul 2013 15:51:48 -0700 [thread overview]
Message-ID: <20130701225148.GC12663@cynthia.pants.nu> (raw)
In-Reply-To: <alpine.LNX.2.00.1307011750540.9202@nippy.intranet>
On Mon, Jul 01, 2013 at 05:54:41PM +1000, Finn Thain wrote:
>
> On Sun, 30 Jun 2013, Brad Boyer wrote:
> >
> > It could become more complicated if we started using the SCC IOP and
> > wanted to be able to do serial console, although I suppose we could use
> > bypass mode until the real driver is loaded later and switch at runtime.
> > It would make some things messy but might still be simpler than
> > complicating this part of the code.
>
> I can't imagine anyone writing an IOP-based SCC driver unless they wanted
> to implement DMA and LocalTalk support. The present code should work fine
> with the pmac_zilog serial driver. It should also work with EARLY_CONSOLE
> if MacOS is configured to put the IOPs into bypass (aka "compatible") mode
> before Penguin boots Linux.
Well, it would be less overhead even for regular serial usage. You wouldn't
need to interrupt the processor as often. But it's probably not worth the
effort. Getting LocalTalk working would be nearly impossible without some
hardware assist such as an IOP (or the PSC-DMA on the models that have it).
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2013-07-01 22:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 9:45 iop_msg_pool Geert Uytterhoeven
2013-06-26 10:48 ` iop_msg_pool Finn Thain
2013-06-26 11:07 ` iop_msg_pool Geert Uytterhoeven
2013-06-26 12:14 ` iop_msg_pool Finn Thain
2013-06-28 8:59 ` iop_msg_pool Geert Uytterhoeven
2013-06-29 4:47 ` iop_msg_pool Finn Thain
2013-06-29 8:15 ` iop_msg_pool Geert Uytterhoeven
2013-07-01 6:57 ` iop_msg_pool Brad Boyer
2013-07-01 7:54 ` iop_msg_pool Finn Thain
2013-07-01 22:51 ` Brad Boyer [this message]
2013-07-01 7:39 ` iop_msg_pool Brad Boyer
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=20130701225148.GC12663@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.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