All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Oe <toe@unlserve.unl.edu>
To: Benjamin Herrenschmidt <bh40@calva.net>
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: update on macserial/DMA
Date: Wed, 6 Oct 1999 08:47:03 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.3.96LJ1.1b7.991006082634.2962A-100000@ofey.inetnebr.com> (raw)
In-Reply-To: <19991006103527.016707@mailhost.mipsys.com>


On Wed, 6 Oct 1999, Benjamin Herrenschmidt wrote:

> It breaks (crash) on the wallstreet's internal modem. The reason is that
> this machines has two SCCs (4 channels) but the device tree only declares
> channel A on the second SCC (so we have only 3 channels visible). This

I see.  That would be a problem.

> breaks the channel cross-references you use to access channel B's
> registers. I'll try to make a simple fix if I find some time today and I
> think I'll just rewrite the probe code by the end of the week or next
> week end since it's too much dependent on the device tree layout.

I've just tried your fix, and, as expected, it causes no harm for PMac
7600.  Thanks.  It's not a big problem, but I think we don't want the
"fake" channel to take up "/dev/ttyS3" or such in case another serial
driver is to be used concurrently.

> 
> BTW. Paul: The patches on my test page (url below + .../test.html)
> include among other things support for the PowerBooks 3400/3500
> ethernet/modem combo interrupt. It looks like there is a second ohare
> chip with cascaded interrupt controller either in the combo itself or on
> the motherboard (or a chip that mimmics the ohare chip). It's not
> referenced by name in the device tree but by vendorid/deviceid. I'm
> wondering if it might contains also an SCC cell for the modem but I can't
> test, I don't have access to one of those machines. I think you have a
> 3400, don't you ? I'll make sure my new probe code can easily be used to

I think ehternet/modem combo is only for the US model of PowerBook
3400/3500.  If Paul had it, the combo should be working a long ago. :)

> declare SCC cells for this kind of cases (but just passing the addresses
> in) just in case...
> 


Takashi Oe


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

  reply	other threads:[~1999-10-06 13:47 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <37F1AD4B.585E99AB@chpc.utah.edu>
1999-09-29  7:11 ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Geert Uytterhoeven
1999-09-29  7:16 ` Takashi Oe
1999-09-29  7:40   ` Geert Uytterhoeven
1999-09-29  9:13   ` Benjamin Herrenschmidt
1999-09-30  0:46     ` Takashi Oe
1999-09-30  8:50       ` Benjamin Herrenschmidt
1999-09-30 16:21         ` Takashi Oe
1999-09-30 16:35           ` Benjamin Herrenschmidt
1999-10-06  5:33             ` update on macserial/DMA Takashi Oe
1999-10-06  8:35               ` Benjamin Herrenschmidt
1999-10-06 13:47                 ` Takashi Oe [this message]
1999-10-06 16:25                   ` Benjamin Herrenschmidt
1999-10-06 16:50                     ` Benjamin Herrenschmidt
1999-10-08  7:13               ` Lou Langholtz
1999-10-09 17:57                 ` Lou Langholtz
     [not found]             ` <Pine.LNX.3.96LJ1.1b7.991005234830.1210A-100000@ofey.inetne br.com>
1999-10-07  9:48               ` Franz Sirl
1999-10-07 15:37                 ` phandel
1999-10-12  7:20       ` [Fwd: Bug: 2.2.12 still hangs PPC after some PPP activity] Lou Langholtz
1999-09-29 16:44   ` Lou Langholtz
1999-09-29 17:02     ` Benjamin Herrenschmidt
1999-09-29 18:08       ` Lou Langholtz
1999-09-29 18:46   ` Lou Langholtz
1999-09-29 20:00   ` Lou Langholtz
1999-09-30  1:14     ` Takashi Oe
1999-09-30  5:33     ` Geert Uytterhoeven
1999-10-01 13:26     ` Franz Sirl
1999-10-01 13:46       ` Alvin Brattli
     [not found]       ` <Pine.OSF.3.96.991001153658.16772E-100000@mitra.phys.uit.no >
1999-10-01 14:08         ` Franz Sirl
1999-10-01 16:14       ` Lou Langholtz

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=Pine.LNX.3.96LJ1.1b7.991006082634.2962A-100000@ofey.inetnebr.com \
    --to=toe@unlserve.unl.edu \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.