From: "Marcus Overhagen" <marcus.overhagen@ims.fhg.de>
To: "Tom Rini" <trini@kernel.crashing.org>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.6 kernel ppc tree
Date: Wed, 18 Feb 2004 18:53:13 +0100 [thread overview]
Message-ID: <007b01c3f648$14ce2bc0$4a34a8c0@av34> (raw)
In-Reply-To: 20040217221957.GH16881@smtp.west.cox.net
"Tom Rini" <trini@kernel.crashing.org> wrote:
> The linuxppc-2.5 tree already has most of this done (as it did as of
> 2.6.1 or 2.6.2, I haven't re-checked the drivers). However, head_8xx.S
> still needs some updates for VM/exception changes.
I tried compiling 2.6.3 for a MPC850 based board today, and got the same problem
with uart.c (as well as a few other minor errors). However, I have trouble getting
the 2.5 uart.c file by bitkeeper, can somebody please send it to me by (private) email?
I also noticed that the Kconfig file, as well as the uart.c file has very few options
to support custom pin assigments, for example I couldn't configure SCC2 as
Ethernet and at the same time SCC3 as serial. Is someone working on this, or
must I do this myself?
And what about hardware handshake signals, like RTS/CTS, does anyone
have that working?
regards
Marcus
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-18 17:53 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 [this message]
2004-02-18 19:07 ` Dan Malek
2004-02-19 10:59 ` Marcus Overhagen
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='007b01c3f648$14ce2bc0$4a34a8c0@av34' \
--to=marcus.overhagen@ims.fhg.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).