LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Chuck Meade'" <chuckmeade@mindspring.com>,
	"'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 23:39:27 +0200	[thread overview]
Message-ID: <001101c68f31$d89aa220$0e67a8c0@Jocke> (raw)
In-Reply-To: <IIEEICKJLNEPBBDJICNGKEFDLDAA.chuckmeade@mindspring.com>

> > 
> > 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

Yes, got one of those.
 
> 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.

hmm, you don't have a patch handy?

> 
> If you are using a newer LTIB release than me, perhaps yours is fixed.
> The one I have is from 3/15/06.

Me too, I have requested that freescale release a new LTIB with proper support,
but who knows when the will be.

> 
> Anyway, this works fine for me and addresses the problem of 
> the platform devs not getting initialized.
> 
> Chuck
> 
> 
> 

  reply	other threads:[~2006-06-13 21:39 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
2006-06-13 21:39       ` Joakim Tjernlund [this message]
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='001101c68f31$d89aa220$0e67a8c0@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=ajz@cambridgebroadband.com \
    --cc=chuckmeade@mindspring.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