From: "Leopold Stotch" <l.butterz@gmail.com>
To: "Grant Likely" <grant.likely@secretlab.ca>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: PSC in UART mode on TQM5200S
Date: Wed, 19 Sep 2007 11:04:12 +0400 [thread overview]
Message-ID: <53b5d6e90709190004o5a84a7d1ve9eece397511ce5a@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40709180701w17273a11wda8c9ece79aad483@mail.gmail.com>
Thank you for the answer, Grant !
I knew nothing about port_config register before your answer :-(
I haven't changed any processor registers yet
because i'm still searching where i can do this.
Can you tell me, is it UBoot specific or kernel specific or both ?
And i already know about MPC5200's device tree in 2.6.x kernel but not
in 2.4.x...
On 9/18/07, Grant Likely <grant.likely@secretlab.ca> wrote:
> On 9/18/07, Leopold Stotch <l.butterz@gmail.com> wrote:
> > Hello, everyone !
> >
> > I have TQM5200S module and development board.
> > It runs factory UBoot and latest DENX's linuxppc_2_4_devel kernel.
> > I want to configure all TQM5200S's onboard PSC's as UART's.
> > TQM5200S's onboard PSC's are connected to custom board
> > that makes all electrical things as my hardware engineer says...
> > So changed
> > $HOME/linuxppc_2_4_devel/arch/ppc/platforms/tqm5200.h
> > the following way:
> >
> > #ifdef CONFIG_PS2MULT
> > #define RS_TABLE_SIZE 4
> > #else
> > #if defined(CONFIG_SPI_EVAL) || defined(CONFIG_TB5200)
> > #define RS_TABLE_SIZE 2
> > #elif defined(CONFIG_CAM5200)
> > #define RS_TABLE_SIZE 6
> > #else
> > #define RS_TABLE_SIZE 3
> > #endif
> > #endif
> >
> > changed to
> >
> > #ifdef CONFIG_PS2MULT
> > #define RS_TABLE_SIZE 4
> > #else
> > #if defined(CONFIG_SPI_EVAL) || defined(CONFIG_TB5200)
> > #define RS_TABLE_SIZE 2
> > #elif defined(CONFIG_CAM5200)
> > #define RS_TABLE_SIZE 6
> > #else
> > #define RS_TABLE_SIZE 6
> > #endif
> > #endif
> >
> > and
> >
> > #else /* default */
> > #define SERIAL_PORT_DFNS \
> > STD_PSC_OP(1) \
> > STD_PSC_OP(2) \
> > STD_PSC_OP(3)
> > #endif
> >
> > changed to
> >
> > #else /* default */
> > #define SERIAL_PORT_DFNS \
> > STD_PSC_OP(1) \
> > STD_PSC_OP(2) \
> > STD_PSC_OP(3) \
> > STD_PSC_OP(4) \
> > STD_PSC_OP(5) \
> > STD_PSC_OP(6)
> > #endif
> >
> > After rebuilding the kernel, dmesg says:
> >
> > ...
> > ttyS0 on PSC1
> > ttyS1 on PSC2
> > ttyS2 on PSC3
> > ttyS3 on PSC4
> > ttyS4 on PSC5
> > ttyS5 on PSC6
> > ...
> >
> > But when i do "echo 1 > /dev/ttyS4" i receive nothing at the other end.
>
> Have you made the appropriate changes to the port_config register?
>
> Cheers,
> g.
>
>
>
> --
> Grant Likely, B.Sc., P.Eng.
> Secret Lab Technologies Ltd.
> grant.likely@secretlab.ca
> (403) 399-0195
>
--
Best regards,
Leopold Stotch
next prev parent reply other threads:[~2007-09-19 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 10:13 PSC in UART mode on TQM5200S Leopold Stotch
2007-09-18 14:01 ` Grant Likely
2007-09-19 7:04 ` Leopold Stotch [this message]
[not found] ` <53b5d6e90709182355y17fd5965u5f212be74068442e@mail.gmail.com>
[not found] ` <fa686aa40709190733ufd38f1fx7771bd0e98376081@mail.gmail.com>
2007-09-19 14:50 ` Leopold Stotch
2007-09-18 22:38 ` Wolfgang Denk
2007-09-19 7:40 ` Leopold Stotch
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=53b5d6e90709190004o5a84a7d1ve9eece397511ce5a@mail.gmail.com \
--to=l.butterz@gmail.com \
--cc=grant.likely@secretlab.ca \
--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).