All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrey Volkov <avolkov@varma-el.com>
To: Olivier Singla <osingla@integrian.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: LITE5200 2.6.x kernel support
Date: Sun, 24 Jul 2005 22:26:01 +0400	[thread overview]
Message-ID: <42E3DD39.8040104@varma-el.com> (raw)
In-Reply-To: <42DE89B1.1030400@integrian.com>

Oliver,

Could you send boot log?
And, at this time, vanilla 2.6.xx kernel couldn't boot from nfs (and use
eth too), since fec (ethernet) driver still not ready.

-- 
Regards
Andrey Volkov

Olivier Singla wrote:
> Hi,
> 
> I am currently using 2.4.25 on the Lite5200 board, but I'd really like to
> switch to 2.6.x. The only 5200 specific support I need are the integrated
> uart and the PCI. I tried both 2.6.11 and 2.6.12 without luck: the kernel
> start, but then is stuck (seems into the init sequence). I use the
> configuration
> file from arch/ppc/configs/lite5200_defconfig. I cross-compiled the
> kernel with gcc-3.4.1.
> 
> I was wondering if somebody could give me some help, maybe by telling
> be what I am doing wrong.
> 
> Thanks,
> Olivier
> 
> BTW, I tried also 2.6.13-rc3, but I can't even compile for the Lite5200,
> there are some syntax error when compile the pci module...
> 
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

  reply	other threads:[~2005-07-24 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-20 17:28 LITE5200 2.6.x kernel support Olivier Singla
2005-07-24 18:26 ` Andrey Volkov [this message]
2005-07-24 21:59   ` Grant Likely
2005-07-26 13:02   ` Kumar Gala
2005-07-26 14:07     ` Andrey Volkov
2005-07-26 14:26       ` Kumar Gala

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=42E3DD39.8040104@varma-el.com \
    --to=avolkov@varma-el.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=osingla@integrian.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.