From: "Chuck Meade" <chuckmeade@mindspring•com>
To: "Joakim Tjernlund" <joakim.tjernlund@transmode•se>,
"'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 17:25:21 -0400 [thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGKEFDLDAA.chuckmeade@mindspring.com> (raw)
In-Reply-To: <000f01c68f2a$68b83960$0e67a8c0@Jocke>
> > 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
Hi Joakim,
Same here -- go into arch/ppc/platforms/83xx and edit file mpc83xx_sys.c.
If you are using the 8323e cpu, then you need to make sure that file has
code to support the 8323E. Mine didn't, so I got no platform devices
initialized (no serial port, no Eth devs). I added a block of code to support
the 8323E (set mask to 0xffff0000 and "value" to 0x80620000, then the
device list for the 8323E). Use existing code there as a guide, it was not
difficult once I figured out that this was the problem.
If you are using a newer LTIB release than me, perhaps yours is fixed.
The one I have is from 3/15/06.
Anyway, this works fine for me and addresses the problem of the platform
devs not getting initialized.
Chuck
next prev parent reply other threads:[~2006-06-13 21:40 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
2006-06-13 21:25 ` Chuck Meade [this message]
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=IIEEICKJLNEPBBDJICNGKEFDLDAA.chuckmeade@mindspring.com \
--to=chuckmeade@mindspring$(echo .)com \
--cc=ajz@cambridgebroadband$(echo .)com \
--cc=galak@kernel$(echo .)crashing.org \
--cc=joakim.tjernlund@transmode$(echo .)se \
--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