linux-kernel - [-mm patch 0/3] Atmel MACB ethernet driver for avr32

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-next>] [day] [month] [year] [list]

Message-ID: <20061107144942.25c2db42@cad-250-152.norway.atmel.com>
Date:	Tue, 7 Nov 2006 14:49:42 +0100
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Andrew Victor <andrew@...people.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: [-mm patch 0/3] Atmel MACB ethernet driver for avr32

Hi,

Here's another driver for Atmel on-chip hardware: the MACB ethernet
controller. This is present in the at32ap7000 chip, as well as (I
think) at91sam926x. It is somewhat similar to the one in at91rm9200,
but the DMA engine is different.

It might make sense to share at least some of the code between the
existing emac driver for at91rm9200 and this one.

As with the spi driver I sent earlier today, I'm including some changes
to avr32 necessary for this driver to actually work. These changes
should go in after the spi changes in the queue or it might conflict.
If this causes any trouble, feel free to just drop them and I'll see if
I can organize things differently.

The last patch in the series adapts the macb driver to the driver model
changes in gregkh-driver-network-device.patch. I didn't fold this into
the driver patch in case someone wants to pick it out and use it on
a 2.6.19-rc kernel.

As always, I really appreciate any comments you may have.

Oh, and this patch even updates MAINTAINERS. I forgot to do that with
the SPI driver, will post an update in a moment.

Haavard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/