From: Lorenz Kolb <linuxppcemb@lkmail•de>
To: linuxppc-embedded@ozlabs•org
Subject: Re: Re: What is the difference between Montavista Kernel Source, and Kernel.Org Source
Date: Sun, 18 Feb 2007 11:20:27 +0100 [thread overview]
Message-ID: <45D8286B.4030900@lkmail.de> (raw)
In-Reply-To: <mailman.1.1171760401.17466.linuxppc-embedded@ozlabs.org>
>> I'm Going to use linux on ML403.
>>
>> I want to know, what is the difference between the linux kernel source,
>> that we download from source.mvista.com ( using git ) and the original
>> kernel source code that we download from kernel.org?
>>
>
> The multiple git trees hosted at source.mvista.com/git are development
> trees similar to the trees hosted at www.kernel.org/git. Contact the
> individual developers for details on each tree.
>
> Dale Farnsworth
>
>
Oh, and I thought that development does mean something like progress.
If I'd "develop" something "new" with last change 8 months ago, I guess
my boss would not pay for that "development".
So what is the difference between kernel.org and montavista's tree for
ML403.
kernel.org is quite a bit ahead.
Personally I'd recommend Denk's 2.6.19 tree (that's a 2.6.19 from
kernel.org with some ppc specific patches, afaik) and patching the EDK
8.2 into it. That's quite a lot of work (I am just doing that at the
moment) but that's the only way to get an up-to-date system.
Currently my partner and I are working on building a minimalistic sound
driver and in some future release a ALSA compliant sound driver and a
new controller (with at least DMA support) as this is can still not be
found in MontaVista.
Lorenz Kolb
next parent reply other threads:[~2007-02-18 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1171760401.17466.linuxppc-embedded@ozlabs.org>
2007-02-18 10:20 ` Lorenz Kolb [this message]
2007-02-20 10:35 ` What is the difference between Montavista Kernel Source, and Kernel.Org Source Vitaly Bordug
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=45D8286B.4030900@lkmail.de \
--to=linuxppcemb@lkmail$(echo .)de \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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