From: "Mark Chambers" <markc@mail.com>
Subject: Re: Linux-2.4.31 porting
Date: Tue, 17 Jan 2006 15:31:09 -0500 [thread overview]
Message-ID: <004f01c61ba4$f77c41e0$6401a8c0@chuck2> (raw)
In-Reply-To: 16FD2D70D281D44F9BFCF6ACF9B6117102AF6570@lisi053a.siemens.pt
Linux-2.4.31 porting
>Hello u all!
> Have you already ported a linux-2.4.31 to be used on a PPC mpc8272
(or anyone from the family) based board?
> The problem that I have is that i don't have console. As far as i
could debug, the kernel stucks on my_console_write (in
arch/ppc/cpm2_io/uart.c), waiting >for transmitter fifo to empty (line
2298 - "while (bdp->cbd_sc & BD_SC_READY)").
> Any suggestions will be highly welcomed!
I have used 2.4.24 running on an mpc8247 based board. My board uses SMC1,
SCC3 and SCC4 for tty,
(console on SCC4) so I had to edit the configuration in uart.c, but no other
changes. You probably have
a configuration mis-match, maybe your parallel port pins are not getting set
up right.
By the way, 2.4.24 put FCC ethernet tables in reserved memory, but I think
that was fixed by 2.4.31.
Check that you have CONFIG_8272 in your .config file to be sure.
Also, I worked from CONFIG_ADS8260 and I couldn't make a bit of sense of the
PCI implementation.
I think the mpc8266ads_pci.c implementation assumes some setup from the
bootloader. I'll be glad to share
what I did (though I'm not very sure of it) if you run into the same
problem.
Mark Chambers
prev parent reply other threads:[~2006-01-17 20:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 19:33 Linux-2.4.31 porting Jose França (Ext_GTBC)
2006-01-17 20:08 ` Vitaly Bordug
2006-01-17 20:31 ` Mark Chambers [this message]
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='004f01c61ba4$f77c41e0$6401a8c0@chuck2' \
--to=markc@mail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.