From: Dmytro Bablinyuk <dmytro.bablinyuk@tait.co.nz>
To: Mark Hatle <fray@mvista.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Linux support for MPC859T processor
Date: Wed, 02 Apr 2003 15:39:21 +1200 [thread overview]
Message-ID: <3E8A5B69.1030601@tait.co.nz> (raw)
In-Reply-To: 3E8A554A.2040700@mvista.com
Yes, we are ready to have a big pain with porting, and we know that
there is a risk which we are trying to reduce.
Would the MontaVista give some hands on, for example, how to an internal
RTC function on '860 represent in the kernel ('859 doesn't have RTC
func) and how it's affect the kernel and how it could be "removed" etc?
So, we at least would know what shall we look for.
Also could you please tell me how assembler on '860 different from '859?
Would this affect booting?
> Honestly, I don't know my guess is close to non to a small handful...
> But I am truely a novice when it comes to CPU/board bringup.. (I've
> assisted in it, but my expertise and history is in userspace
> development.) The things that can take massive amounts of time on
> these new processors/boards are hardware bugs (cpu and board) as well
> as device drivers for new on chip devices. I have seen more then one
> engineer going bald due to hardware bugs, especially a board that the
> customer said "But it runs VxWorks, why doesn't it run Linux?"...
>
>> Not a lot of our people experienced in PPC assembler (including myself).
>> Actually not a lot experienced with PPC at all.
>> Roughly, from your point of you, how major changes in the kernel
>> could be? Just your subjective opinion.
>>
>>> On userspace basis.. the 860 and the 859 are fully compatable.. The
>>> need for
>>> 859T changes may be in the kernel. So anyone who sells/supports an
>>> 860 based
>>> system can support your needs for application level. (That includes
>>> MontaVista.)
>>>
>>> The linux kernel of course is a different level of complexity.
>>>
>>>> We are trying to find a linux supplier who supports Motorola MPC859T
>>>> processor (actually it will be processor from Motorola but our custom
>>>> board).
>>>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-02 3:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 2:31 Linux support for MPC859T processor Dmytro Bablinyuk
2003-04-02 2:45 ` Mark Hatle
2003-04-02 3:05 ` Dmytro Bablinyuk
2003-04-02 3:13 ` Mark Hatle
2003-04-02 3:39 ` Dmytro Bablinyuk [this message]
2003-04-02 18:15 ` Conn Clark
2003-04-03 8:59 ` Frank Robbins
-- strict thread matches above, loose matches on Subject: below --
2003-04-02 14:41 Jean-Denis Boyer
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=3E8A5B69.1030601@tait.co.nz \
--to=dmytro.bablinyuk@tait.co.nz \
--cc=fray@mvista.com \
--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).