LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Pantelis Antoniou <panto@intracom.gr>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.6 on 8xx (was [PATCH] Driver for FECs on motorola DUET (87x/88x))
Date: Tue, 25 May 2004 11:06:32 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0405251104470.7779@localhost.localdomain> (raw)
In-Reply-To: <40B35372.9080201@intracom.gr>


On Tue, 25 May 2004, Pantelis Antoniou wrote:

>
> Robert P. J. Day wrote:

> >i'm definitely interested in what it took for you to get this to work.
> >currently, i've got a perfectly working system, booting a 2.4-based
> >kernel, compiled with ELDK 3.0, on a customized 8xx board.  this system
> >uses the now-deprecated "devfs".
> >
> I used an NFS mounted root ELDK 3.0 filesystem. By mistake I booted with
> devfs and everything worked except the telnet networked logins.
> Did not have time to check why though.

oh, so devfs, although deprecated, will still work?  that's good to know,
one less thing i need to fight with.

> >i bk-cloned the linuxppc-2.5 tree, did "make menuconfig" as best i could
> >(guessing every so often at some of the new features), compiled a new
> >kernel and, glory be, actually got the new kernel to boot up to the point
> >of trying to start "init", at which point it hung.
> >
> Well you wont get any further than this using the stock kernel.
>
> I had to use my own ethernet and a ported over serial uart driver for CPM2
> boards.
>
> Also some tweaking is needed to the irq dispatch and defining out
> some mmu staff which do not apply for 8xx.

ok, i'll just hang out and wait for changes to eventually appear.  no
big rush on my part.  thanks.

rday

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

      reply	other threads:[~2004-05-25 15:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 14:42 [PATCH] Driver for FECs on motorola DUET (87x/88x) Pantelis Antoniou
     [not found] ` <40A4C04A.8060508@intracom.gr>
2004-05-14 14:22   ` Joakim Tjernlund
2004-05-14 14:14     ` Pantelis Antoniou
2004-05-14 14:48   ` Pantelis Antoniou
2004-05-14 15:23     ` Joakim Tjernlund
2004-05-14 15:18       ` Pantelis Antoniou
2004-05-14 15:32       ` Tom Rini
2004-05-14 21:52   ` Dan Malek
2004-05-24 13:40     ` Pantelis Antoniou
2004-05-24 17:18       ` Dan Malek
2004-05-24 19:11         ` Joakim Tjernlund
2004-05-25  1:10         ` Paul Mackerras
2004-05-25  9:49           ` Joakim Tjernlund
2004-05-25 10:24             ` Paul Mackerras
     [not found]         ` <40B327EF.2090903@intracom.gr>
2004-05-25 14:01           ` 2.6 on 8xx (was [PATCH] Driver for FECs on motorola DUET (87x/88x)) Robert P. J. Day
2004-05-25 14:08             ` Pantelis Antoniou
2004-05-25 15:06               ` Robert P. J. Day [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=Pine.LNX.4.58.0405251104470.7779@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=panto@intracom.gr \
    /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