All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Diggs <kevdig@hypersurf.com>
To: linuxppc-dev@ozlabs.org
Subject: Re: pmac_zilog debugging ...
Date: Thu, 13 Nov 2008 14:29:06 -0800	[thread overview]
Message-ID: <491CAA32.20307@hypersurf.com> (raw)
In-Reply-To: <1226612654.7178.84.camel@pasglop>

Benjamin Herrenschmidt wrote:
> On Thu, 2008-11-13 at 03:38 -0800, Kevin Diggs wrote:
> 
> 
>>12,206 PowerMac Zilog interrupts
>>
>>Interrupt load is higher without the DMA support.
>>
>>Is it possible that this hardware was not meant to be used without the
>>DMA (i.e. it does not work quite right?)?
> 
> 
> Well, the HW Rx buffer is only 3 bytes so if you have high interrupt
> latencies you are more likely to loose data...
> 
These are not real 8530s any more, right? How certain are we of this?
Is it possible that there is a larger buffer when used with the DMA
capability ... somehow?

> Now, as I said, have you looked at flow control ? It's a likely cause of
> problems and it's possible that pmac_zilog doesn't do it the way
> macserial did...
> 
I tried to put some debug statements where the flow lines are managed. I
could have goofed it up. They never produce any output. The latest
attempt used nortscts which should have disabled flow control. That
coupled with the fact that a 250 MHz 750GX is talking to a 486dx4 at
1200 - 9600 baud I would have thought would reduce the chance the PowerMac
would fall behind?

> Regarding DMA, it's possible to implement, though there were interesting
> issues with the way it was done in macserial, it should be done
> differently in pmac_zilog.
> 
> I think the only approach that really works properly (though it's fugly)
> is what Apple does in OSX I think, which is to have a DMA descriptor per
> input byte (no need for a huge DMA buffer anyway).
> 
You would need to explain to me the advantage of doing DMA in this case???

> Cheers,
> Ben.
> 
> 

  reply	other threads:[~2008-11-13 22:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-07 21:38 pmac_zilog debugging Kevin Diggs
2008-11-07 22:23 ` Benjamin Herrenschmidt
2008-11-13 11:38   ` Kevin Diggs
2008-11-13 21:44     ` Benjamin Herrenschmidt
2008-11-13 22:29       ` Kevin Diggs [this message]
2008-11-14  1:00         ` Benjamin Herrenschmidt
2008-11-17  8:37           ` Kevin Diggs
2008-11-17  9:00             ` Benjamin Herrenschmidt
2008-11-17 10:21               ` Kevin Diggs
2008-11-17 11:40                 ` Benjamin Herrenschmidt
2008-11-08  5:52 ` Paul Mackerras
2008-11-08 10:46   ` Benjamin Herrenschmidt

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=491CAA32.20307@hypersurf.com \
    --to=kevdig@hypersurf.com \
    --cc=linuxppc-dev@ozlabs.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.