linux-kernel - Re: [PATCH RFC] misc/at24: distinguish between eeprom and fram chips

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]

Message-Id: <201301281140.15289.poeschel@lemonage.de>
Date:	Mon, 28 Jan 2013 11:40:15 +0100
From:	Lars Poeschel <poeschel@...onage.de>
To:	Wolfram Sang <w.sang@...gutronix.de>
Cc:	gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
	linux-i2c@...r.kernel.org
Subject: Re: [PATCH RFC] misc/at24: distinguish between eeprom and fram chips

On Thursday 24 January 2013 at 08:27:01, Wolfram Sang wrote:
> > > > > > I wanted to use a fm24c04 i2c fram chip with linux. I grepped
> > > > > > the source and found nothing. I later found that my chip can be
> > > > > > handled by at24 eeprom driver. It creates a sysfs file called
> > > > > > eeprom to read from and write to the chip. Userspace has no
> > > > > > chance to distinguish if it is writing an eeprom or a fram
> > > > > > chip.
> > > > > 
> > > > > Why should it?
> > > > 
> > > > Because writes are much faster and it doesn't have to take care on
> > > > erase cycles. It could use other write strategies on such devices
> > > > and update informations that have to survive power downs more
> > > > often.
> > > 
> > > I agree. I think that a seperate attribute named e.g. 'page_size'
> > > would be more helpful than renaming the binary file to fram?
> > 
> > Yes, this is a much better solution! Adding a seperate sysfs file
> > page_size and a file for the type of device which would read eeprom,
> > fram, etc then. If you also think this is the way to go, I would spent
> > one of my next free timeslots to this.
> 
> Oops, this mail seems to have dropped off :(

Luckily I did not have a free timeslot to invest yet. ;)

> I am all for the 'page_size' attribute, but still not convinced what
> gain the 'type' attribute would allow. For FRAM, the page size will be
> large. Isn't this enough information?

Yes, this would be enough information and I think this is the way we should 
go.
I set this on my todo list. Although the change will be quite simple, I think 
I will not find the time to hit the upcoming merge window.

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