linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: John Linn <John.Linn@xilinx.com>
To: "Peter Korsgaard" <jacmet@sunsite.dk>, "swamydp" <swamydp@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: linux 2.6 hangs at __delay function on Viretx 4 board
Date: Wed, 4 Jun 2008 15:22:31 -0600	[thread overview]
Message-ID: <20080604212233.37F44130004F@mail123-sin.bigfish.com> (raw)
In-Reply-To: <87tzg97f5l.fsf@macbook.be.48ers.dk>

Hi Peter,

Yes you need to enable UARTLITE as the console in the kernel
configuration.

You have the command line syntax, ttyUL0, correct.

They have now changed the UART 16550 to be a free core in the EDK, not
sure which version of the EDK that happened.

Thanks,
John

-----Original Message-----
From: linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org
[mailto:linuxppc-embedded-bounces+john.linn=3Dxilinx.com@ozlabs.org] On
Behalf Of Peter Korsgaard
Sent: Wednesday, June 04, 2008 2:56 AM
To: swamydp
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: linux 2.6 hangs at __delay function on Viretx 4 board

>>>>> "swamydp" =3D=3D swamydp  <swamydp@gmail.com> writes:

 swamydp> Hi John

 swamydp> I am using UARTLITE as serial console. I do not have license
 swamydp> for UART 16550.  I have enabled the drivers for uartlite in
 swamydp> menuconfig while configuring the kernel. I have tested all
 swamydp> combinations for the kernel command line - tty0, ttyUL0,
 swamydp> ttyl0, ttyS0 but could not get uartlite to output kernel
 swamydp> printk messages.

Correct syntax is console=3DttyUL0

 swamydp> Since I am using uartlite , the following settings are
 swamydp> turned off in menuconfig

 swamydp> CONFIG_SERIAL_8250=3Dn
 swamydp> CONFIG_SERIAL_8250_CONSOLE=3Dn

Do you have console on uartlite (CONFIG_SERIAL_UARTLITE_CONSOLE)
enabled?

-- =

Bye, Peter Korsgaard
_______________________________________________
Linuxppc-embedded mailing list
Linuxppc-embedded@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-embedded


This email and any attachments are intended for the sole use of the named r=
ecipient(s) and contain(s) confidential information that may be proprietary=
, privileged or copyrighted under applicable law. If you are not the intend=
ed recipient, do not read, copy, or forward this email message or any attac=
hments. Delete this email message and any attachments immediately.

  reply	other threads:[~2008-06-04 21:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14  3:29 linux 2.6 hangs at __delay function on Viretx 4 board swamydp
2008-05-14 15:01 ` John Linn
2008-05-16 14:56   ` swamydp
2008-05-16 16:28     ` John Linn
2008-05-25  5:35       ` swamydp
2008-05-27  4:11         ` swamydp
2008-05-28 14:07           ` John Linn
2008-06-04  3:00             ` swamydp
2008-06-04  8:55               ` Peter Korsgaard
2008-06-04 21:22                 ` John Linn [this message]
2008-06-04 21:31                   ` Peter Korsgaard
2008-06-04 21:44                   ` Howard, Marc
2008-06-04 23:18                     ` Stephen Neuendorffer
2008-06-19 16:33 ` swamydp

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=20080604212233.37F44130004F@mail123-sin.bigfish.com \
    --to=john.linn@xilinx.com \
    --cc=jacmet@sunsite.dk \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=swamydp@gmail.com \
    /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).