public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Vitaly Bordug <vbordug@ru•mvista.com>
To: KokHow Teh <KokHow.Teh@marconi•com>
Cc: david.jander@protonic•nl,
	linuxppc-embedded list <linuxppc-embedded@ozlabs•org>
Subject: Re: serial console
Date: Wed, 05 Oct 2005 16:23:39 +0400	[thread overview]
Message-ID: <4343C5CB.2040006@ru.mvista.com> (raw)
In-Reply-To: <OF0BB1D8FC.27908478-ON48257091.000E28F8@uk.marconicomms.com>

KokHow Teh wrote:
> Hi;
>       I have tried with 4 types of command lines with my linux kernel with
> devfs and serial device compiled in and none gives me the desired results:
> 
> (1)   console=tts/0,115200n8 OR console=ttyCPM0,115200n8
> 
>       no serial console output at all during boot time but it gives me
> login prompt at the end.
> 
> (2)   without "console=" OR console=ttyS0,115200n8
> 
>       serial console output fine during bootup but only until the point
> when it prints out "Freeing unused kernel memory: 232k init 4k prep". After
> that, the serial console output is garbled. No login prompt.
> 
>       So this has not solved my problem. I need more advice. Here are some
> more questions and observations:
> 
> (1)   David Jander's comment:
> 
> I don't know exactly what I am talking about right now, but the string
> "tts/0"
> in the console-line sounds suspicious to me. AFAIK when using devfs still
> device names on the kernel-commandline have to be old-style.
> Just a guess: try using "console=ttyS0,115200n8" and see if this helps.
> 
>       Is it confirmed that kernel-commandline has to be old-style even
> though the kernel is using devfs?
> 
> (2)   Vitaly Bordug's suggestion of using "console=ttyCPM0". May I know
> where is ttyCPM0 defined and how is it bound to the serial console device
> driver in the source?
> 
Ummm.. The driver itself is in drivers/serial/cpm_uart. It does have the 
different major than ordinary ttyS... This relates to the 2.6.x kernel 
of course. I could suggest you to try the latest kernel.org release, in 
which you board is known to work fine.

>       Thanks for any input and pointer.
> 
> Regards,
> TEH
> 
> 
> 


-- 
Sincerely,
Vitaly

  reply	other threads:[~2005-10-05 12:23 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-05  2:36 serial console KokHow Teh
2005-10-05 12:23 ` Vitaly Bordug [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-10-05  2:32 KokHow Teh
2005-10-04  6:54 KokHow Teh
2005-10-04 15:11 ` David Jander
2005-10-04 15:16   ` Vitaly Bordug
2005-10-05  9:16     ` David Jander
2005-07-30  1:06 Serial console Daniel Ann
2005-07-30  1:19 ` Josh Boyer
2005-07-30  1:36   ` Daniel Ann
2005-07-30  5:46     ` Daniel Ann
2005-07-30  1:27 ` Ricardo Scop
2005-07-30  1:34   ` Daniel Ann
2005-07-30 10:37 ` Anton Wöllert
2005-08-01  1:27   ` Daniel Ann
2005-08-02  3:38     ` JohnsonCheng
2005-08-02 13:39       ` Kumar Gala
2005-08-03  0:16         ` Daniel Ann
2003-03-04 14:53 Serial Console Aman
2003-03-04 15:40 ` Mark Hatle
2003-03-04 17:06   ` Ibon Gotxi Garcia
2003-03-04 19:09     ` Dave Wolfe
2003-01-16 21:06 Aman

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=4343C5CB.2040006@ru.mvista.com \
    --to=vbordug@ru$(echo .)mvista.com \
    --cc=KokHow.Teh@marconi$(echo .)com \
    --cc=david.jander@protonic$(echo .)nl \
    --cc=linuxppc-embedded@ozlabs$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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