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


Thank you.  However, since I started out with the 2.2.13 sources and found
they just didn't work really at all on the CLLF (a driver bug somewhere?  I've
never done the diffs to try to find out.), I abandoned that approach and
relucantly went with the source tree you posted.  As you pointed out earlier
today, going with the real (ftp.kernel.org) source trees has huge advantages if
you can make it work for you.  But I failed on that path.

Now I'm wondering if I'll encounter the same sorts of difficulties with the
2.3.x kernel (2.3.18 might be the best place to start?).  Do you have a feeling
for whether the CLLF board will work with 2.3.18?  Certainly the 2.2.13 from
the ftp.us.kernel.org did NOT work, even configured precisely as your kernel
was configured.

Thanks very much, Dan.  You're helping me a LOT.  I hope someday to be able to
give back what I'm taking during this process, but I gotta get started first.

a

On Wed, 26
Jan 2000, Dan Malek wrote: > Alan Mimms wrote: >  > >
> > 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.
>
> The last 2.3.xx kernel I used was 2.3.18.  Since I have customers
> building real products, all I have been using is 2.2.13.
>
> Recently, I have been trying to get 2.3.xx updated with 8xx
> modifications (like the FEC for the CLLF), but I have been
> spending time just making the current tree build properly.
>
> If you want 8xx that works, use the 2.2.13 kernel, and update
> the FEC driver from the source on ppc.kernel.org.  That is all
> I have been using for months.
>
>
> 	-- 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 21:06 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
2000-01-26 19:36     ` Dan Malek
2000-01-26 21:06       ` Alan Mimms [this message]
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=00012613095603.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).