Hello,
On 13 January 2015 at 12:34, Vladimir Komendantskiy
komendant...@gmail.com wrote:
I tested the driver with a different Hynix chip, and it worked. Same driver,
same DTB but with my original Hynix chip causes the same this NULL pointer
error. Here are the extended IDs for the reference:
Soldered onto the variant with no flash. I patched MTD NAND code in U-Boot,
the old stable kernel and mtd-utils to support the non-standard 16KiB page
size.
Vladimir
On Feb 2, 2015 1:38 PM, Michal Suchanek hramr...@gmail.com wrote:
Hello,
On 13 January 2015 at 12:34, Vladimir Komendantskiy
Hi Michal,
On my hardware, when the NAND driver loads OK, there are still anomalies:
the used by count is -2 in lsmod output for all MTD modules.
# lsmod
Module Size Used by
ofpart 2048 -2
sunxi_nand 18325 -2
ofnandpart 1476 -2
nand
I tested the driver with a different Hynix chip, and it worked. Same
driver, same DTB but with my original Hynix chip causes the same this NULL
pointer error. Here are the extended IDs for the reference:
Works fine:
{H27UBG8T2BTR 4GiB 3.3V 8-bit,
{ .id = {0xad, 0xd7, 0x94, 0xda, 0x74, 0xc3} },
On 13 January 2015 at 12:34, Vladimir Komendantskiy
komendant...@gmail.com wrote:
I tested the driver with a different Hynix chip, and it worked. Same driver,
same DTB but with my original Hynix chip causes the same this NULL pointer
error. Here are the extended IDs for the reference:
Works
Hello,
On 12 January 2015 at 17:59, Vladimir Komendantskiy
komendant...@gmail.com wrote:
Hi Michal,
Thanks for your patch. I tested it, arriving at the same result as before
(with mainline 3.19) except for your version is set to ignore real bad
blocks, which I hope was a temporary solution.
Can you help me understand this strange bug on a10s-olinuxino-m? I guess my
DT record for NAND MTD partitions is somehow incorrect because I happen to
get a kernel panic in the mainline 3.19 kernel that looks like this:
[0.599782] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xde
[
On 9 January 2015 at 18:16, Vladimir Komendantskiy
komendant...@gmail.com wrote:
Can you help me understand this strange bug on a10s-olinuxino-m? I guess my
DT record for NAND MTD partitions is somehow incorrect because I happen to
get a kernel panic in the mainline 3.19 kernel that looks like
Hello,
I tried to rebase the v7 patchset on top of 3.18 and add the DT
bindings on cubieboard:
https://github.com/hramrach/linux-sunxi/commit/a946d593ddcf443b0f035f6d39fe0c558189dacc
The nand driver fails equally on both cubieboard versions:
cubieboard:
[0.643554] calling
tis 2014-12-16 klockan 19:01 +0100 skrev Michal Suchanek:
Hello,
I tried to rebase the v7 patchset on top of 3.18 and add the DT
bindings on cubieboard:
https://github.com/hramrach/linux-sunxi/commit/a946d593ddcf443b0f035f6d39fe0c558189dacc
The nand driver fails equally on both cubieboard
10 matches
Mail list logo
