All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Phillip Lougher <phillip@lougher.demon.co.uk>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc_2_4_devel vs MontaVista STB3xxxx kernel
Date: Wed, 21 Nov 2001 22:28:31 -0500	[thread overview]
Message-ID: <3BFC70DF.4040905@embeddededge.com> (raw)
In-Reply-To: Pine.LNX.4.21.0111220032220.1377-100000@lougher.demon.co.uk


Phillip Lougher wrote:


> I am now left wondering whether it may be better to move over to
> the 2_4_devel kernel for the STB3xxxx and for further kernel
> work I need to do for different 4xx chips.

It depends upon what kind of support you want.  If you want to do
everything yourself and hope some of your questions are answered here,
then the _devel kernel is probably OK.  If you want real Linux
technicians dedicated to answer your questions and provide help when
you ask then the MontaVista subscription is for you.  Also, IBM
provides drivers only to STB customers for all of their specialty
peripherals in the chips.  These drivers and other software are only
available with the MontaVista distribution, we don't have access to
this or ability to maintain them in the public sources.

The boards containing STB processors aren't generally available. All of
the software in the public _devel tree is courtesy of MontaVista
employees as their time permits.  You may have to contribute and test
changes to keep the public tree up to date.

Thanks.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-11-22  3:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-22  0:59 linuxppc_2_4_devel vs MontaVista STB3xxxx kernel Phillip Lougher
2001-11-22  3:28 ` Dan Malek [this message]

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=3BFC70DF.4040905@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=phillip@lougher.demon.co.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.