From: "Marcus Overhagen" <marcus.overhagen@ims•fhg.de>
To: "Dan Malek" <dan@embeddededge•com>
Cc: <linuxppc-embedded@lists•linuxppc.org>
Subject: Re: 2.6 kernel ppc tree
Date: Thu, 19 Feb 2004 11:59:55 +0100 [thread overview]
Message-ID: <001601c3f6d7$8291ca60$4a34a8c0@av34> (raw)
In-Reply-To: 4033B7DB.8050905@embeddededge.com
"Dan Malek" <dan@embeddededge•com> wrote:
> Marcus Overhagen wrote:
>
> > I tried compiling 2.6.3 for a MPC850 based board today,
>
> OK, everyone, just wait a day or so.......
Ok, you convinced me. I'll wait until VM updates are done :)
Thanks to Rod Boyce, who sent me the 2.5 uart.c I tried compiling.
I also noticed that some defines for enet.c were missing from commproc.h
and these errors:
| arch/ppc/kernel/entry.S(__ksymtab+0x3e0): undefined reference to `request_8xxirq'
| arch/ppc/syslib/built-in.o: In function `m8xx_calibrate_decr':
| arch/ppc/syslib/built-in.o(.init.text+0x124): undefined reference to `request_8xxirq'
| arch/ppc/syslib/built-in.o(.init.text+0x124): relocation truncated to fit: R_PPC_REL24 request_8xxirq
> The 8xx stuff hasn't worked at all for a long time......if ever.
Well, it was working in 2.4.4 as publish in ELDK 2.1 at www.denx.de
However, the uart.c driver in that package has some enhancements,
compared to the mainline 2.4.25 kernel (or it was removed for 2.4.25)
Especially the ability to configure a wide variety of different pins, and
hardware handshake.
Unfortunately, RTS handshake as implemented in 2.4.4 is not working
with the MPC850, since the MPC850 doesn't do a correct UART like
RTS signal, instead it activates /RTS only during transmit. I need to fix
that, and will wait with 2.6 until you are finished.
Luckily, MPC850 can do at least a correct /CTS handshake when bit FLC
in registert PSMR is set, and you can control /RTS in UART like fashion
by programming it as general IO pin.
> Tom fixed up the drivers for me, I'm working on the VM updates.
Thats great.
> Stop trying to compile it and complaining about it because it
> is known to not work properly :-)
Yeah, now I know :) BTW, this is not a complaint!
Marcus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-19 10:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 21:30 2.6 kernel ppc tree Rod Boyce
2004-02-17 21:47 ` Mike Welliington
2004-02-17 22:19 ` Tom Rini
2004-02-18 17:53 ` Marcus Overhagen
2004-02-18 19:07 ` Dan Malek
2004-02-19 10:59 ` Marcus Overhagen [this message]
2004-02-19 17:46 ` Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 19:08 Rod Boyce
2004-02-18 1:13 Rod Boyce
2004-02-18 19:03 ` Tom Rini
2004-02-17 21:55 Rod Boyce
2004-02-17 21:22 Lokesh Kumar
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='001601c3f6d7$8291ca60$4a34a8c0@av34' \
--to=marcus.overhagen@ims$(echo .)fhg.de \
--cc=dan@embeddededge$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.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