linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brendan John Simon <Brendan.Simon@ctam.com.au>
To: Dan Malek <dmalek@jlc.net>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: linuxppc-embedded: main kernel tree
Date: Thu, 27 Jan 2000 05:31:01 +1100	[thread overview]
Message-ID: <388F3D65.3B420FED@ctam.com.au> (raw)


Hi Dan,

How seperate is the Linux/PPC kernel tree to the main kernel tree ?

I download linux-2.2.14 and there is only support for MBX (no BSEIP and
others).  I'm not sure if the MBX is the latest either.  I suspect it
hasn't changed much anyway.

Can support for all the embedded ports be put into the main kernel
source tree.
That way we can all use the latest stable kernel without having to wait
for you (or someone else) to create a package on the ftp server.  It
also reduces the re-porting of board support packages.

How often is the Linux/PPC kernel for workstations (PowerMacs, etc)
committed to the main kernel tree ?

Thanks,
Brendan Simon.


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

             reply	other threads:[~2000-01-26 18:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-26 18:31 Brendan John Simon [this message]
2000-01-26 15:55 ` linuxppc-embedded: main kernel tree Dan Malek
2000-01-26 19:00   ` Alan Mimms
2000-01-26 19:36     ` Dan Malek
2000-01-26 21:06       ` Alan Mimms
2000-01-26 21:30         ` Dan Malek
2000-01-26 21:45           ` Alan Mimms
2000-01-27  0:45           ` Graham Stoney
2000-01-26 22:36     ` Bill Roman
2000-01-27 22:09       ` Cort Dougan
2000-01-27  0:58     ` Graham Stoney
2000-01-27  1:53       ` Jeremy Fitzhardinge
2000-01-27 22:06   ` Cort Dougan

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=388F3D65.3B420FED@ctam.com.au \
    --to=brendan.simon@ctam.com.au \
    --cc=dmalek@jlc.net \
    --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).