public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
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 18:01:12 -0400	[thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGCEFHLDAA.chuckmeade@mindspring.com> (raw)
In-Reply-To: <001101c68f31$d89aa220$0e67a8c0@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?

Here you go:

--- mpc83xx_sys.c-ORIG	2006-06-13 17:54:36.577339832 -0400
+++ mpc83xx_sys.c	2006-06-13 17:56:02.394293672 -0400
@@ -136,6 +136,23 @@ struct ppc_sys_spec ppc_sys_specs[] = {
 #endif
 		},
 	},
+	{
+		.ppc_sys_name	= "8323E",
+		.mask		= 0xFFFF0000,
+		.value		= 0x80620000,
+#ifdef CONFIG_QE
+		.num_devices	= 4,
+#else
+		.num_devices	= 2,
+#endif
+		.device_list	= (enum ppc_sys_devices[])
+		{
+			MPC83xx_IIC1, MPC83xx_DUART,
+#ifdef CONFIG_QE
+			MPC83xx_QE_UCC3, MPC83xx_QE_UCC4,
+#endif
+		},
+	},
 	{	/* default match */
 		.ppc_sys_name	= "",
 		.mask 		= 0x00000000,


Regards,
Chuck

  reply	other threads:[~2006-06-13 22:00 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
2006-06-13 22:01         ` Chuck Meade [this message]
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=IIEEICKJLNEPBBDJICNGCEFHLDAA.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