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 12:13:22 +0200 [thread overview]
Message-ID: <87d59syxj1.fsf@sleipner.barco.com> (raw)
In-Reply-To: <2FE3DBF1797A1443AAB3FA0EF6BF4EEC021EA645@XSJ-EXCHVS1.xlnx.xilinx.com> (John Bonesio's message of "Thu, 14 Sep 2006 18:40:53 +0200")
>>>>> "JB" == John Bonesio <john.bonesio@xilinx.com> writes:
Hi,
JB> << The Xilinx approach of overwriting the source tree just feels
JB> wrong, and no one seems to want to do it that way.>>
JB> I am in the group that has control over how this is done. What
JB> would you propose be done different? Keep in mind that we are
JB> trying to support a process where someone builds a hardware design
JB> and the later changes it with new peripherals or perhaps makes
JB> minor tweaks. We want to make the updating of the Linux kernel to
JB> reflect these hardware changes easy for people.
Don't patch the kernel sources from EDK, but instead get the drivers
integrated in the mainline kernel. Either do config options for the
various IP versions or use runtime detection.
We're doing Linux development for several platforms and using a single
kernel tree for it all is absolute critical to my sanity..
The EDK drivers are nice as examples of how to use the IP cores, but
the defined and documented interface should be the IP, not the EDK
drivers.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2006-09-19 10:13 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 16:40 Ethernet driver for Linux kernel 2.6 running on ML403 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 [this message]
2006-09-19 18:06 ` Andrew
-- strict thread matches above, loose matches on Subject: below --
2006-09-15 19:13 John Bonesio
2006-09-19 14:16 ` Grant Likely
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.
[not found] <mailman.241.1158193867.2423.linuxppc-embedded@ozlabs.org>
2006-09-14 1:40 ` 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
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.
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=87d59syxj1.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 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.