From: Wang Yong <wung_y@263.net>
To: Grant Erickson <grant@lcse.umn.edu>
Cc: linuxppc embedded mail list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: TiVo Kernel for 403GCX Update (was Re: Support for IBM CPUs?)
Date: Sun, 24 Oct 1999 18:57:40 +0800 [thread overview]
Message-ID: <3812E624.BF756DFF@263.net> (raw)
In-Reply-To: Pine.SGI.4.10.9910222012050.46619-100000@brule.lcse.umn.edu
Hi,
It appears you compiled this kernel with GCC, so i am wondering if
GCC could work correctly with some architecture specified instructions
of
PPC embedded controller? Do you know if GCC could compile the kernel
written
for 401D2, another embedded controller from IBM? this is very important
for
us because we're starting to port linux to this platform(RedWood3) but
we still don't know which compiler should be ok.
Regards,
Wang
Grant Erickson wrote:
>
> I've made some progress since Wednesday with the TiVo source code. As I
> mentioned previously, the TiVo Linux kernel is based on the 2.1.24 PowerPC
> sources. However, after comparing the tree against both stock 2.1.24 and
> 2.2.12 trees, it appears they've borrowed code from more recent trees and
> HEAVILY modified the 2.1.24 code in others.
>
> They have configurations for both the TeleWorld Consumer Device (TCD) and
> the TeleWorld Consumer Device Eval Board (TCD_EVAL). The latter of these
> is presumed to be the IBM PowerPC 403GCX "Oak" evaluation board.
>
> Included in arch/ppc are two configuration files, devconf and prodconf,
> one presumably for development/manufacturing configurations and the other
> for released product in the field (I've included devconf below).
>
> Compiling this with the LATEST released set of GNU tools and the GCC
> 2.95.1 compiler was pretty straightforward using the 'devconf'
> configuration as a base and then adding "CONFIG_TCD_EVAL=y" for my IBM
> evaluation board.
>
> The only major changes required were to drivers/char/serial.c (which is
> changed dramatically from stock) and arch/ppc/tcd/qdma.c (a DMA engine for
> their Audio, Video, and disk controllers).
>
> Anyway, I was able to successfully load the kernel to the IBM evaluation
> board using the tftpboot functionality in the IBM-supplied PROM; however,
> the system froze after a few instructions.
>
> Time to hook up the ICE and figure out where things are stopping...
>
> Getting most of the changes into the 2.3.x development tree shouldn't be
> too difficult. I've got some preliminary stuff done. What is the best
> protocol to follow, submit the patches to the list for general evaluation
> and dissemination or send them to Cort and then everyone call grab them
> from vger?
>
> Anyone else out there call up TiVo and get their source code yet?
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-24 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 11:44 Support for IBM CPU's ? daniel.n.nilsson
1999-10-13 14:59 ` Grant Erickson
1999-10-13 21:13 ` Wolfgang Denk
1999-10-13 21:54 ` Grant Erickson
1999-10-14 5:13 ` Grant Erickson
1999-10-14 14:40 ` Adrian Cox
1999-10-18 21:38 ` Daniel Nilsson
1999-10-18 23:24 ` Jason Haas
1999-10-20 20:03 ` Support for IBM CPUs? Grant Erickson
1999-10-23 1:32 ` TiVo Kernel for 403GCX Update (was Re: Support for IBM CPUs?) Grant Erickson
1999-10-23 7:55 ` Wolfgang Denk
1999-10-23 16:37 ` TiVo Webmaster
1999-11-12 3:12 ` Wang Yong
1999-11-18 1:33 ` TiVo Webmaster
1999-10-24 10:57 ` Wang Yong [this message]
1999-10-25 14:33 ` Marcus Sundberg
1999-10-18 23:38 ` Support for IBM CPU's ? Grant Erickson
[not found] <B43E0634.1BD%mfryar@gcctech.com>
1999-10-28 18:04 ` TiVo Kernel for 403GCX Update (was Re: Support for IBM CPUs?) Grant Erickson
[not found] <Pine.SGI.4.10.9910281200550.695157-100000@sapphire.lcse.umn.edu>
1999-10-28 18:13 ` Jason Haas
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=3812E624.BF756DFF@263.net \
--to=wung_y@263.net \
--cc=grant@lcse.umn.edu \
--cc=linuxppc-embedded@lists.linuxppc.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).