Dear Stefan Roese,
In message 201010221239.36387...@denx.de you wrote:
+static phys_addr_t __cfi_flash_bank_size(int i)
+{
+#ifdef CONFIG_SYS_FLASH_BANKS_SIZES
+ return ((unsigned long [])CONFIG_SYS_FLASH_BANKS_SIZES)[i];
+#else
+ return 0;
+#endif
+}
+phys_addr_t
Dear Ilya Yanok,
In message 1287674413-3900-5-git-send-email-ya...@emcraft.com you wrote:
On some boards we have flash mapped high in the address space with
considerably small window (say 0xFE00 and 32MB). When we install
bigger chip (say 64MB) on such a board strange things happen
Hi Ilya,
On Thursday 21 October 2010 17:20:12 Ilya Yanok wrote:
On some boards we have flash mapped high in the address space with
considerably small window (say 0xFE00 and 32MB). When we install
bigger chip (say 64MB) on such a board strange things happen
(flash_write() doesn't work at
On some boards we have flash mapped high in the address space with
considerably small window (say 0xFE00 and 32MB). When we install
bigger chip (say 64MB) on such a board strange things happen
(flash_write() doesn't work at all, for ex). That's because cfi_flash
driver doesn't care about
Dear Stefan,
In message 1287674413-3900-5-git-send-email-ya...@emcraft.com you wrote:
On some boards we have flash mapped high in the address space with
considerably small window (say 0xFE00 and 32MB). When we install
bigger chip (say 64MB) on such a board strange things happen
5 matches
Mail list logo
