From: "Steven J. Hill" <sjhill@realitydiluted.com>
To: SANTHOSH K <santhoshk@nestec.net>
Cc: "'linux-mips@linux-mips.org'" <linux-mips@linux-mips.org>
Subject: Re: QUERY: Porting Linux kernel to Toshiba TX4927
Date: Mon, 24 Feb 2003 07:46:35 -0600 [thread overview]
Message-ID: <3E5A223B.5020505@realitydiluted.com> (raw)
In-Reply-To: <F6E1228667B6D411BAAA00306E00F2A5153A6F@pdc2.nestec.net>
SANTHOSH K wrote:
>
> 1. Has somone already ported Linux to TX4927 chip?
>
Yes, we (TimeSys) have already done this.
> 2. If not, what is the complexity of this wor?
>
Oh, it was a pretty interesting port. The PCI code is
pretty awful.
> 3. If yes, then who is maintaining it. We could not get any information from
> the source tree.
>
We will actively maintain it.
> 4. If yes, is it an open source? where can I get the source code.
>
The code should be released in the next couple of months.
-Steve
next prev parent reply other threads:[~2003-02-24 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 16:28 QUERY: Porting Linux kernel to Toshiba TX4927 SANTHOSH K
2003-02-24 13:46 ` Steven J. Hill [this message]
2003-02-24 17:34 ` Pete Popov
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=3E5A223B.5020505@realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=linux-mips@linux-mips.org \
--cc=santhoshk@nestec.net \
/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