From: Daniel Ann <ktdann@gmail.com>
To: "Anton Wöllert" <a.woellert@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Serial console
Date: Mon, 1 Aug 2005 10:27:00 +0900 [thread overview]
Message-ID: <9b7ca65705073118276e89b29@mail.gmail.com> (raw)
In-Reply-To: <42EB587D.80403@gmail.com>
Thanks for your input Anton.
I'm not all that certain about sandpoint platform has its own serial
driver so I've worked with 8250.c. Anyway, I've got it working now. It
was problem with interrupt. As soon as I changed interrupt from EGDE
to LEVEL it began working. Altho I'm faced with yet another problem
with openpic but I'm digging thru it at the moment.
BTW, I have no idea why EDGE didnt work and LEVEL does.
Cheers,
Daniel
On 7/30/05, Anton W=F6llert <a.woellert@gmail.com> wrote:
> Daniel Ann wrote:
> > Hi folks,
> >
> > Having all the kernel boot up log on console means that I've done some
> > part right. But why am I not getting anything from the user processes
> > on the console screen ?
> >
> > Is there anything I need to do on the kernel config ?
> >
>=20
> Hi, we've had the same problem some time ago on a tqm850l (mpc850). Our
> problem was, that we had registered two serial consoles in the kernel
> config or something like that. we had to disable all serial-driver stuff
> and enable just the platform-specific serial-console driver. we tracked
> this down with inserting a printk(buf) into the tty_write fs-op of the
> serial-port driver in drivers/char/tty_io.c. the ttyS0 was used but has
> taken another serial-driver than the platform specific.
>=20
> may this help you :)
>=20
>=20
> anton
>=20
--=20
Daniel
next prev parent reply other threads:[~2005-08-01 1:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2005-08-02 3:38 ` JohnsonCheng
2005-08-02 13:39 ` Kumar Gala
2005-08-03 0:16 ` Daniel Ann
-- strict thread matches above, loose matches on Subject: below --
2005-10-05 2:36 serial console KokHow Teh
2005-10-05 12:23 ` Vitaly Bordug
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
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=9b7ca65705073118276e89b29@mail.gmail.com \
--to=ktdann@gmail.com \
--cc=a.woellert@gmail.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).