linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Mimms <alan@packetengines.com>
To: Dan Malek <dan@netx4.com>, Brendan.Simon@ctam.com.au
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc-embedded: main kernel tree
Date: Wed, 26 Jan 2000 11:00:46 -0800	[thread overview]
Message-ID: <00012611055301.05597@alan.corp.packetengines.com> (raw)
In-Reply-To: <388F18F5.BDE5D395@netx4.com>


Dan,

Can you suggest a version of the 2.3.x kernel that WOULD build and work?  Is
there a simple way to retrieve it (i.e., one I can get from ftp.us.kernel.org)?
I have tried 2.3.34 and found that the 'make menuconfig' and all other ways of
simply generating a config were broken for powerpc in ways that I wasn't able
to understand.  (Looked like a missing endif or some such, but I was never sure
even after a couple of hours of study.)

What kernel source version from the "main" tree actually builds and works
pretty well for most/all of the 8xx platforms?  I am particularly interested in
the CLLF supporting kernel.

I can live with 2.3.x since I don't need ramdisk support for my intended
application.  In fact, I'm very interested in the new cramfs I have read about
as a solution for our flash based file system.  I'll probably dink with that a
bit next chance I get.

Thanks for any info...
a

On Wed, 26 Jan
2000, Dan Malek wrote: > Brendan John Simon wrote:
>
>
> > How seperate is the Linux/PPC kernel tree to the main kernel tree ?
>
> It isn't supposed to be, but.....
>
>
> > I download linux-2.2.14 and there is only support for MBX
>
>
> ....I have never merged the later 8xx updates from the 2.3.xx
> ttree into 2.2.xx.  The amount of change is a concern for a "stable"
> tree, and the couple of occasions I had the time to do this the
> tree was locked for update with Linus.  It is on my "to do" list.
>
>
> > Can support for all the embedded ports be put into the main kernel
> > source tree.
>
> The "main" tree is really the 2.3.xx tree right now, and all of
> the 8xx support is there.  For some reason, the BitKeeper 2.3.41
> version doesn't build.  I fixed a couple of problems, but now I
> am wondering if it will build for any PMac platform.......
>
>
> > 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.
>
>
> The only reason I put things on the server was for people that
> couldn't get access to a source tree for some reason.  I don't
> like to do that, but people got used to it so I continued.  I
> may continue to do so only for a 2.2.xx version.
>
>
> > also reduces the re-porting of board support packages.
>
> We don't have board support packages.......It just reminds me
> of horrible hacks people make so they don't have to provide
> source code.  With complete source code available, we have
> to find a better way (and use better terminology).
>
>
> > How often is the Linux/PPC kernel for workstations (PowerMacs, etc)
> > committed to the main kernel tree ?
>
> Every day?  I have the same complaint most people have expressed
> lately.  I work in the BitKeeper tree, which is supposed to be
> the official PPC tree and one step away from kernel.org.  I can't
> build it for any of my systems.  I have to go looking for something
> from Paul or Ben or someone else to get something to work......
>
> With 2.4.xx soon to happen, we should all be working from the
> latest 2.3.xx tree from kernel.org.  If it doesn't work (which
> is the case now at least for me), it must be quickly corrected.
>
> I copied linuxppc-dev on this message....so what's the deal with
> all PPC sources?  When (and from where) will I be able to download
> a kernel tree that I can build for anything?
>
> Thanks.
>
>
> 	-- Dan
--
Alan Mimms     Packet Engines, Inc.     Spokane, Washington [99214-0497]
  USA, Earth, Sol, Milky Way, The Local Group, Virgo Supercluster, U0
Despite the cost of living, have you noticed how popular it remains?
  -- Steven Wright?

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

  reply	other threads:[~2000-01-26 19:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-26 18:31 linuxppc-embedded: main kernel tree Brendan John Simon
2000-01-26 15:55 ` Dan Malek
2000-01-26 19:00   ` Alan Mimms [this message]
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=00012611055301.05597@alan.corp.packetengines.com \
    --to=alan@packetengines.com \
    --cc=Brendan.Simon@ctam.com.au \
    --cc=dan@netx4.com \
    --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).