linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: diekema_jon <diekema@bucks.si.com>
Cc: Dan Malek <dan@penguin.netx4.com>,
	linuxppc-embedded@lists.linuxppc.org,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: Trying to find out the current state of Linux on a MPC 8260
Date: Fri, 05 Nov 1999 14:45:36 -0500	[thread overview]
Message-ID: <382333E0.1F57B795@netx4.com> (raw)
In-Reply-To: m11jo7O-001SwNC@bucks


diekema_jon wrote:


> What CVS archives do you update?

I have access to the vger CVS tree, and only update the minimal
embedded 8xx and 82xx files.  I rely heavily (and thankfully :-)
on others to ensure these changes are propagated into Linus'
and other trees.


> What are the collection names that contains the updates?  Is it just "linux"?


Yes, for the kernel.

I think it is time to remind everyone finding, compiling and booting
a kernel is actually the easy part of the development effort.  The
real challenges are the applications.....creating the development
environment with compiler, libraries, debuggers and other tools
is time consuming.  I try to make the embedded things I do work
as closely to a desktop or server as possible, but there are
sometimes differences.



	-- Dan

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

      reply	other threads:[~1999-11-05 19:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-05 14:59 Trying to find out the current state of Linux on a MPC 8260 diekema_jon
1999-11-05 18:59 ` Dan Malek
1999-11-05 18:29   ` diekema_jon
1999-11-05 19:45     ` 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=382333E0.1F57B795@netx4.com \
    --to=dan@netx4.com \
    --cc=dan@penguin.netx4.com \
    --cc=diekema@bucks.si.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --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).