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]
Date:	Thu, 10 May 2007 23:19:33 +0200
From:	Thomas Gleixner <tglx@...utronix.de>
To:	David Brownell <david-b@...bell.net>
Cc:	Hans-Jürgen Koch <hjk@...utronix.de>,
	dwmw2@...radead.org, Andrew Victor <andrew@...people.com>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: drivers/mtd/devices/at91_dataflash26.c

David,

On Thu, 2007-05-10 at 13:07 -0700, David Brownell wrote:
> On Friday 27 April 2007, David Brownell wrote:
> > On Friday 27 April 2007, Hans-Jürgen Koch wrote:
> > 
> > > > 	 the m25p80 driver
> > > > was pretty close to working with those Atmel devices too ...
> > > > most of the commands are identical.
> > > 
> > > Thanks for that hint, I'll have a look at the data sheet.
> 
> Any progress on that?  I looked again, and yes most commands
> are identical.
> 
>  - That driver relies on an AT91-only SPI stack that's not
>    going upstream, instead of drivers/spi/atmel_spi.c;
> 
>  - Driver can't even be selected on kernel.org kernel (!!);
> 
>  - The m25p80 driver will need at most minor tweaks to
>    handle those AT26 (and AT25) series chips;
> 
> So 340ea370c2ce89d1c15fbf785460f2f74314ce58 should be reverted.

We look into this and fix the problem. There is no need to revert it
right now. It does no harm and we remove it with the merge into the
m25p80 driver, ok ?

	tglx


-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ