linux-kernel - Re: [PATCH 0/3] at91

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 26 Sep 2006 11:48:26 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	Andrew Victor <andrew@...people.com>
Cc:	Russell King <rmk+lkml@....linux.org.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] at91_serial: Introduction

On 26 Sep 2006 11:28:11 +0200
Andrew Victor <andrew@...people.com> wrote:

> hi Haavard,
> 
> > Maybe we can agree on a platform_data format so
> > that we can remove the #ifdef altogether?
> 
> The platform_data structure is currently defined in
> include/asm-arm/arch-at91rm9200/board.h as:
> 
> struct at91_uart_data {
> 	short	use_dma_tx;	/* use transmit DMA? */
> 	short	use_dma_rx;	/* use receive DMA? */
> };
> 
> I don't think the DMA-support is currently in mainline, but is in the
> pending patches on http://maxim.org.za/AT91RM9200/2.6/

Are you going to submit it for 2.6.19? I want to try to slam a big
rename patch in without messing up too many not-yet-submitted patches...

> I guess we can just add another field:
> 	short	no_remap;	/* base address is already
> mapped */ (or something similar)

Or maybe even better:
	void __iomem *regs;	/* fixed mapping of base address */

to indicate the actual mapping (if it's NULL, it hasn't been mapped yet)

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/