From: Peter Korsgaard <jacmet@sunsite.dk>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Ethernet driver for Linux kernel 2.6 running on ML403
Date: Tue, 19 Sep 2006 09:48:58 +0200 [thread overview]
Message-ID: <87hcz4z47p.fsf@sleipner.barco.com> (raw)
In-Reply-To: <528646bc0609140734j2f7b008fy815f221677c5ac74@mail.gmail.com> (Grant Likely's message of "Thu, 14 Sep 2006 16:34:22 +0200")
>>>>> "GL" == Grant Likely <grant.likely@secretlab.ca> writes:
Hi,
GL> So what direction do we (as the community) want to go for
GL> supporting Xilinx IP in the Linux kernel?
GL> IIRC, Xilinx intends to get drivers submitted into mainline.
GL> (Based on their cross-platform driver support code). It is
GL> unknown which and how many drivers for different IP versions will
GL> be submitted.
Yes, that's also what I hear from the Xilinx guys - But action speaks
louder than words. It's not like the V2P is new technology anymore.
GL> However, the xilinx driver code is verbose and does not match well
GL> with the rest of the Linux code base.
Yeah, the Xilinx stuff/flow definately doesn't fit the kernel.
GL> If we reject the Xilinx driver code, then we either have to do
GL> without Xilinx support in mainline, or we need to write new
GL> drivers that address the above issues (support multiple IP
GL> versions, etc). The Xilinx support in mainline right now does not
GL> use any Xilinx code. (Xilinx PIC and UART).
I think the best option is to simply forget about the Xilinx code,
see the FPGAs as any other PPC system and write normal device drivers
for it. Your platform bus stuff and my (to-be-mainlined) uartlite
driver is a first step in this direction..
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2006-09-19 7:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.241.1158193867.2423.linuxppc-embedded@ozlabs.org>
2006-09-14 1:40 ` Ethernet driver for Linux kernel 2.6 running on ML403 Aleck Lin
2006-09-14 1:48 ` Eugene Surovegin
2006-09-14 1:52 ` Grant Likely
2006-09-14 11:18 ` David H. Lynch Jr.
2006-09-14 13:53 ` Michael Galassi
2006-09-14 14:34 ` Grant Likely
2006-09-14 15:47 ` Keith J Outwater
2006-09-14 22:57 ` Grant Likely
2006-09-19 7:48 ` Peter Korsgaard [this message]
2006-09-19 14:17 ` Grant Likely
2006-09-19 20:10 ` Grant Likely
2006-09-19 20:40 ` David H. Lynch Jr.
2006-09-19 21:27 ` Grant Likely
2006-09-24 5:42 ` David H. Lynch Jr.
2006-09-24 14:35 ` Grant Likely
2006-09-14 23:02 ` David H. Lynch Jr.
2006-09-14 16:40 John Bonesio
2006-09-14 17:36 ` Keith J Outwater
2006-09-14 22:02 ` T Ziomek
2006-09-14 23:16 ` David H. Lynch Jr.
2006-09-14 22:49 ` Grant Likely
2006-09-15 16:11 ` T Ziomek
2006-09-19 10:13 ` Peter Korsgaard
2006-09-19 18:06 ` Andrew
-- strict thread matches above, loose matches on Subject: below --
2006-09-14 17:52 John Bonesio
2006-09-14 23:08 ` Keith J Outwater
2006-09-15 0:08 ` David H. Lynch Jr.
2006-09-15 1:14 ` David H. Lynch Jr.
2006-09-15 19:13 John Bonesio
2006-09-19 14:16 ` Grant Likely
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=87hcz4z47p.fsf@sleipner.barco.com \
--to=jacmet@sunsite.dk \
--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).