From: "colin" <colin@realtek.com.tw>
To: <linux-mips@linux-mips.org>
Subject: Which MIPS kernel is good to start up? linux-mips.org or Montavista?
Date: Tue, 26 Oct 2004 15:08:34 +0800 [thread overview]
Message-ID: <007801c4bb2a$9e7ded90$8b1a13ac@realtek.com.tw> (raw)
Hi all,
We want to begin to put Linux to our new board with 4KEc CPU.
Is it better to start porting from Montavista's Kernel, or from the one of
linux-mips.org?
I phoned the sales of Montavista and he told me the difference of these 2
kernels are little, but their kernels have been tested a lot for stability.
Naturally, we would like to choose the kernel version above 2.6.
Thanks and regards,
Colin
WARNING: multiple messages have this Message-ID (diff)
From: "colin" <colin@realtek.com.tw>
To: linux-mips@linux-mips.org
Subject: Which MIPS kernel is good to start up? linux-mips.org or Montavista?
Date: Tue, 26 Oct 2004 15:08:34 +0800 [thread overview]
Message-ID: <007801c4bb2a$9e7ded90$8b1a13ac@realtek.com.tw> (raw)
Message-ID: <20041026070834.PaVRb0LxHoK6BWiU5Ee5kXZ9sgMeudXsZoi8HkRDIY4@z> (raw)
Hi all,
We want to begin to put Linux to our new board with 4KEc CPU.
Is it better to start porting from Montavista's Kernel, or from the one of
linux-mips.org?
I phoned the sales of Montavista and he told me the difference of these 2
kernels are little, but their kernels have been tested a lot for stability.
Naturally, we would like to choose the kernel version above 2.6.
Thanks and regards,
Colin
next reply other threads:[~2004-10-26 7:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-26 7:08 colin [this message]
2004-10-26 7:08 ` Which MIPS kernel is good to start up? linux-mips.org or Montavista? colin
2004-10-26 7:11 ` Pete Popov
2004-10-26 16:10 ` Manish Lachwani
2004-10-26 16:14 ` Pete Popov
2004-10-27 3:14 ` Ralf Baechle
2004-10-27 6:11 ` colin
2004-10-27 6:11 ` colin
2004-10-27 6:20 ` 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='007801c4bb2a$9e7ded90$8b1a13ac@realtek.com.tw' \
--to=colin@realtek.com.tw \
--cc=linux-mips@linux-mips.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