netdev - Re: [RFC patch] driver for the Opencores Ethernet Controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200612041827.kB4IRqrW019090@oogie-boogie.ics.uci.edu>
Date:	Mon, 04 Dec 2006 10:27:52 -0800
From:	Dan Nicolaescu <dann@....uci.edu>
To:	Lennert Buytenhek <buytenh@...tstofly.org>
Cc:	netdev@...r.kernel.org
Subject: Re: [RFC patch] driver for the Opencores Ethernet Controller

Lennert Buytenhek <buytenh@...tstofly.org> writes:

  > On Mon, Dec 04, 2006 at 10:01:01AM -0800, Dan Nicolaescu wrote:
  > 
  > > The Opencores Ethernet Controller is Verilog code that can be used to
  > > implement an Ethernet device in hardware. It needs to be coupled with
  > > a PHY and some buffer memory. Because of that devices that implement
  > > this controller can be very different. The code here tries to support
  > > that by having some parameters that need to be defined at compile
  > > time.
  > 
  > Considering this, why don't you make it a platform driver?

I didn't know about "platform drivers" before your mail. I guess I
could convert it to that if that is the right thing to do. 
(It might be an overkill given that the device is kind of simple and
embedded people prefer small code...)

Any comments on the driver itself? 

Thanks
        --dan
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html