From: Alex Zeffertt <ajz@cambridgebroadband.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: 2.4.18: CPM1 stops when initializing ATM/UTOPIA.
Date: Mon, 9 May 2005 13:10:00 +0100 [thread overview]
Message-ID: <20050509131000.38afa58a.ajz@cambridgebroadband.com> (raw)
In-Reply-To: <427BBA71.8040307@chello.nl>
It may be that you're getting a conflict in SCC usage. Make sure you
have CONFIG_SERIAL_ATM undefined. But if you really need it make sure
CONFIG_SERIAL_ATM_SCC is not used by anything else. You may also want
to disable CONFIG_PTP_SWITCHING if you don't need it. Finally you
probably want CONFIG_PHY_OTHER instead of CONFIG_PHY_SUNI_155 or
CONFIG_PHY_ATM_25. These latter options make assumptions about the
memory mapping of your phy.
Note: a long while ago we had problems with PTP switching causing hangs
but this was fixed by a ucode patch from motorola. If you really need
PTP switching you should get this.
Alex
On Fri, 06 May 2005 20:41:53 +0200
Theo Gjaltema <gjalt007@chello.nl> wrote:
> Hi,
>
> Last week I was trying to integrate the atm/utopia driver
> (sourceforce) into a 2.4.18 kernel build for a 862, but mij attemtps
> failed. It appeared that wen on the first location of the SCC4 (now
> used for utopia) a buffer address is written, most CPM activities are
> halted, including the SCM1 which I used as console port. The console
> driver did write in the allocated buffer descriptors, but the
> tranmission of the data was never acknowledged, thus hanging the
> kernel.
>
> Anyone an idea what happened?
>
> Theo.
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2005-05-09 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 18:41 2.4.18: CPM1 stops when initializing ATM/UTOPIA Theo Gjaltema
2005-05-09 12:10 ` Alex Zeffertt [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=20050509131000.38afa58a.ajz@cambridgebroadband.com \
--to=ajz@cambridgebroadband.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).