From: Ameet Patil <ammubhai@gmail.com>
To: Benjamin Heyne <benjamin.heyne@uni-dortmund.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: XUPV2P, which kernel 2.6. device drivers are available?
Date: Mon, 07 Aug 2006 17:03:22 +0100 [thread overview]
Message-ID: <44D7644A.5070107@gmail.com> (raw)
In-Reply-To: <20060807172251.1d4e81bd@bob.dt.e-technik.uni-dortmund.de>
Hi Benjamin,
I had ported the ENET driver but it was a bit buggy. Could you send
me your driver patch so I can test it?
Thanks,
-Ameet
Benjamin Heyne wrote:
> Hi all,
> despite having problems with zlib, I'd like to know which
> device drivers for the XUPV2P have already been ported
> to the 2.6 kernel? - I don't want to do work twice ;-).
>
> For practicing, I just ported the original Xilinx ENET 100MBit
> driver (seems to work in FIFO mode, including MII - At least I
> can mount and use a NFS root file system)...but that has probably
> already been done elsewhere. I saw that work is going on for
> the SystemACE. - So what about VGA, AC97, PS/2, SATA?
>
> Best regards
> Benjamin Heyne
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
next prev parent reply other threads:[~2006-08-07 16:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 8:02 XUPV2P, Kernel 2.6.17 boot problem Benjamin Heyne
2006-08-01 11:21 ` Ameet Patil
2006-08-02 19:50 ` David H. Lynch Jr.
2006-08-04 14:00 ` Peter Korsgaard
2006-08-04 15:35 ` David H. Lynch Jr.
2006-08-07 7:40 ` Peter Korsgaard
2006-08-07 9:46 ` Benjamin Heyne
2006-08-07 15:22 ` XUPV2P, which kernel 2.6. device drivers are available? Benjamin Heyne
2006-08-07 16:03 ` Ameet Patil [this message]
2006-08-11 8:30 ` Benjamin Heyne
-- strict thread matches above, loose matches on Subject: below --
2006-08-09 18:02 stevea-mdi
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=44D7644A.5070107@gmail.com \
--to=ammubhai@gmail.com \
--cc=benjamin.heyne@uni-dortmund.de \
--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 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).