linux-kernel - Re: [PATCH 0/2] New NAND chip IDs

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: <55B79CCD.5000804@redhat.com>
Date:	Tue, 28 Jul 2015 17:16:29 +0200
From:	Hans de Goede <hdegoede@...hat.com>
To:	Boris Brezillon <boris.brezillon@...e-electrons.com>
Cc:	Michal Suchanek <hramrach@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Brian Norris <computersforpeace@...il.com>,
	Petros Angelatos <petrosagg@...il.com>,
	linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] New NAND chip IDs

Hi,

On 07/28/2015 05:10 PM, Boris Brezillon wrote:
> Hi Hans,
>
> On Tue, 28 Jul 2015 16:49:58 +0200
> Hans de Goede <hdegoede@...hat.com> wrote:
>
>> Hi,
>>
>> On 07/28/2015 04:29 PM, Michal Suchanek wrote:
>>> Hello,
>>>
>>> the NAND chips on Cubietech boards are not known to Linux.
>>>
>>> I used Petros Angelatos' patch from sunxi experimental tree for one chip and
>>> added another chip.
>>>
>>> I hope it's ok to send both patches to avoid merge conflict.
>>
>> I do not think that these patches are a good idea, this will lead to an
>> ever growing manual maintained list of ids, and that is not maintainable
>> IMHO.
>>
>> For Samsung chips we only need the ecc strength and size the rest is already
>> detected on the fly, and I've a patch in my personal tree to get the
>> ecc strengt and size from the nand without needing to have an entry per
>> chip:
>>
>> https://github.com/jwrdegoede/linux-sunxi/commit/53b335d33232753b7aa70298009158baadf5a6bf
>>
>> This is IMHO a much better solution.
>
> Hm, IMHO it's not: the nand ids table also store information about
> supported NAND timings, and maybe we'll have to add new things (like
> the read-retry implementation to use for a specific chip).
>
> Moreover, this information can be automatically deduced from the NAND
> id, and we try to keep discoverable info out of the DT.

Note I'm not advocating to add stuff to DT, I'm advocating to not
add entries to the ID table unless it gives us something which we
cannot get another way.

The current samsung nand entries in the table only add ecc strength /
size info over what is already determined by the generic nand scan code,
my patch adds support to get ecc strength / size for samsung nands to
the generic code, this allows at least to remove the current samsung
nand lines, I believe.

Regards,

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