All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ameet Patil <ammubhai@gmail.com>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6 kernel on XUPV2pro / ML300 board!
Date: Wed, 28 Jun 2006 18:50:03 +0100	[thread overview]
Message-ID: <44A2C14B.5070504@gmail.com> (raw)

Hi,
   I have a XUPV2Pro Xilinx Embedded PPC405 board which is similar in 
many respects to the ML3XX series. With good support in the kernel 
source tree, I was easily able to compile the 2.4.26 linux kernel to run 
on it.

However, I wanted 2.6 kernel to run on it. For some reason, the Xilinx 
drivers and the OCP code went missing in the 2.6 kernel tree.
Does anyone know why did 2.6 kernel drop the Xilinx ML300 board
drivers (SysACE, Ethernet, Frame Buffer) which were present in the 2.4
kernel code tree? It is because of porting issues?

Anyway, I have ported the old 2.4 Xilinx drivers (Sysace and Ethernet) 
to 2.6.17.1 kernel. If anyone is interested to test them, please let me 
know. I shall put out a patch soon...

Thanks,
-Ameet

             reply	other threads:[~2006-06-28 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 17:50 Ameet Patil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-28 18:42 2.6 kernel on XUPV2pro / ML300 board! Rick Moleres

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=44A2C14B.5070504@gmail.com \
    --to=ammubhai@gmail.com \
    --cc=linuxppc-embedded@ozlabs.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 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.