LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Kumar Gala'" <galak@kernel.crashing.org>,
	"'Alex Zeffertt'" <ajz@cambridgebroadband.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: No ttyS device at I/O port 0xfe004500 for console
Date: Tue, 13 Jun 2006 22:46:13 +0200	[thread overview]
Message-ID: <000f01c68f2a$68b83960$0e67a8c0@Jocke> (raw)
In-Reply-To: <2CFF4933-A9D2-4981-BD11-C38537CE193B@kernel.crashing.org>

> On Jun 13, 2006, at 11:48 AM, Alex Zeffertt wrote:
> 
> > Hi list,
> >
> > I'm trying to boot a linux-2.6.11 kernel on a MPC83xx based 
> board.   
> > Through
> > some experimentation I have found I need 
> "console=uart,io,0xfe004500"
> > in the kernel command line in order to get any output over 
> the serial 
> > port.
> >
> > Half way through initialisation the kernel appears to swap from its 
> > "early"
> > 8250 serial driver to a "full" 8250 serial driver.  At this 
> point it 
> > prints "No ttyS device at I/O port 0xfe004500 for console" 
> and there 
> > is no further output.
> >
> > Does anyone have any idea what I may be doing wrong?
> >
> > BTW, here's the output that I do get.
> 
> Alex, where did you get this 2.6.11 kernel?  The public tree 
> didn't have support for 83xx in 2.6.11.  I'd suggest looking 
> at using something newer like 2.6.16 and see if you have the 
> same issue.

I suspect he got from the same place I did, freescales LTIB dev. env.
which has been patched to support 832x. I am having the same problem as he
has, any info on what the problem might be would be great.

Also, if anyone has any info on when these patches will be sent upstream, I 
sure would like to hear about it.

 Jocke

  reply	other threads:[~2006-06-13 20:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 16:48 No ttyS device at I/O port 0xfe004500 for console Alex Zeffertt
2006-06-13 19:55 ` Kumar Gala
2006-06-13 20:46   ` Joakim Tjernlund [this message]
2006-06-13 21:25     ` Chuck Meade
2006-06-13 21:39       ` Joakim Tjernlund
2006-06-13 22:01         ` Chuck Meade
2006-06-13 22:32           ` Kumar Gala
2006-06-14  9:00             ` Alex Zeffertt
2006-06-13 23:53           ` Joakim Tjernlund
2006-06-14  0:19             ` Joakim Tjernlund
2006-06-14  2:27               ` Chuck Meade
2006-06-14  8:47   ` Alex Zeffertt
2006-06-13 21:20 ` Joakim Tjernlund
2006-06-14  8:51   ` Alex Zeffertt
  -- strict thread matches above, loose matches on Subject: below --
2006-06-14 12:37 Joakim Tjernlund
2006-06-14 14:04 ` Chuck Meade

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='000f01c68f2a$68b83960$0e67a8c0@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=ajz@cambridgebroadband.com \
    --cc=galak@kernel.crashing.org \
    --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