From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by ozlabs.org (Postfix) with ESMTP id C28C067B69 for ; Fri, 15 Sep 2006 08:57:42 +1000 (EST) Received: by ug-out-1314.google.com with SMTP id 30so103372ugc for ; Thu, 14 Sep 2006 15:57:40 -0700 (PDT) Message-ID: <528646bc0609141557s4c126f4fh61f1ca8a21a628ad@mail.gmail.com> Date: Thu, 14 Sep 2006 16:57:40 -0600 From: "Grant Likely" Sender: glikely@gmail.com To: "Keith J Outwater" Subject: Re: Ethernet driver for Linux kernel 2.6 running on ML403 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed References: <528646bc0609140734j2f7b008fy815f221677c5ac74@mail.gmail.com> Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 9/14/06, Keith J Outwater wrote: > > > > So what direction do we (as the community) want to go for supporting > > Xilinx IP in the Linux kernel? > > I don't know about anyone else, but running Linux on Virtex FPGAs is > something I simply have to be able to do. With or without Xilinx > drivers, I think the kernel needs to support Xilinx hardware. ditto > > > > > If we reject the Xilinx driver code, then we either have to do without > > Xilinx support in mainline, or we need to write new drivers that > > address the above issues (support multiple IP versions, etc). The > > Xilinx support in mainline right now does not use any Xilinx code. > > (Xilinx PIC and UART). > > > > Thoughts? > > As painful as it may be, maybe we just write drivers from scratch and > try to track changes in the IP. That's kind of the direction I'm leaning too. -- Grant Likely, B.Sc. P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195