linux-kernel - Re: [-mm patch 3/4] AVR32 MTD: Mapping driver for the ATSTK1000board

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: <20060915095629.22cf01f4@cad-250-152.norway.atmel.com>
Date:	Fri, 15 Sep 2006 09:56:29 +0200
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	David Woodhouse <dwmw2@...radead.org>
Cc:	Andrew Morton <akpm@...l.org>, linux-mtd@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [-mm patch 3/4] AVR32 MTD: Mapping driver for the
 ATSTK1000board

On Thu, 14 Sep 2006 21:11:28 +0100
David Woodhouse <dwmw2@...radead.org> wrote:

> On Thu, 2006-09-14 at 16:32 +0200, Haavard Skinnemoen wrote:
> > Add mapping driver for the AT49BV6416 NOR flash chip on the
> > ATSTK1000 development board. 
> 
> Hm, can't you set it up in advance and just register a platform_device
> for physmap to drive?

Probably. I'll give it a try.

I have to find a way to unlock the flash at some point, though. Is it
okay if I add code to physmap to iterate over the partitions and unlock
the writable ones if info->mtd->unlock is non-null? Or is there a
better way to do it?

Andrew, please don't merge any of the patches in this series. I just
noticed that the SMC patch should be cleaned up a bit, so I'm
probably going to rework all the patches.

(btw, I got an "awaiting moderator approval" message from the linux-mtd
mailer because "Message has a suspicious header". Can someone tell me
more about this so I can fix my mailer?)

Thanks,

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/