Hello Boris,
thanks for the fast response.
Am 15.11.2018 um 16:15 schrieb Boris Brezillon:
Hi Heiko,
On Thu, 15 Nov 2018 15:21:31 +0100
Boris Brezillon wrote:
Looks like spi_flash_mtd_register() is doing something really bad here
Yes!
[1]: memsetting the global sf_mtd_info object witho
Hello Boris,
Am 15.11.2018 um 17:47 schrieb Boris Brezillon:
On Thu, 15 Nov 2018 16:15:51 +0100
Boris Brezillon wrote:
Hi Heiko,
On Thu, 15 Nov 2018 15:21:31 +0100
Boris Brezillon wrote:
Looks like spi_flash_mtd_register() is doing something really bad here
[1]: memsetting the global sf_
On Thu, 15 Nov 2018 16:15:51 +0100
Boris Brezillon wrote:
> Hi Heiko,
>
> On Thu, 15 Nov 2018 15:21:31 +0100
> Boris Brezillon wrote:
>
> >
> > Looks like spi_flash_mtd_register() is doing something really bad here
> > [1]: memsetting the global sf_mtd_info object without testing if
> > this
Hi Heiko,
On Thu, 15 Nov 2018 15:21:31 +0100
Boris Brezillon wrote:
>
> Looks like spi_flash_mtd_register() is doing something really bad here
> [1]: memsetting the global sf_mtd_info object without testing if
> this object has already been registered, and then registering it again
> to the MT
On Thu, 15 Nov 2018 14:48:49 +0100
Marek Vasut wrote:
> On 11/15/2018 11:14 AM, Heiko Schocher wrote:
> > Hello all,
> >
> > just see with current HEAD of u-boot on an imx6ull based board with SPI NOR
> > and NAND following behaviour:
>
> +CC Boris, since he was recently looking into this stu
On 11/15/2018 11:14 AM, Heiko Schocher wrote:
> Hello all,
>
> just see with current HEAD of u-boot on an imx6ull based board with SPI NOR
> and NAND following behaviour:
+CC Boris, since he was recently looking into this stuff.
> => mtdparts
>
> device nand0 , # parts = 1
> #: name
Hello all,
just see with current HEAD of u-boot on an imx6ull based board with SPI NOR
and NAND following behaviour:
=> mtdparts
device nand0 , # parts = 1
#: namesizeoffset mask_flags
0: ubi 0x0800 0x 0
device nor0 ,
Hi,
I'm trying to build a u-boot binary containing default configuration.
I created my configuration include file:
```
#define MTDIDS_DEFAULT "nand0=nand_flash"
#define MTDPARTS_DEFAULT
"mtdparts=nand_flash:256k(bootstrap)ro,512k(uboot)ro,256k(env1),256k(env2),-(sys)"
#define CONFIG_BOOT
On 02/11/2011 10:06 AM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> please do not top post / full quote; please read
> http://www.netmeister.org/news/learn2quote.html
Sorry
> In message<4d54eb92.7080...@ftemaximal.fr> you wrote:
>> I will try to write my own driver for my board.
> You alm
Dear Alexandre Gambier,
please do not top post / full quote; please read
http://www.netmeister.org/news/learn2quote.html
In message <4d54eb92.7080...@ftemaximal.fr> you wrote:
>
> I will try to write my own driver for my board.
You almost certainly do not have to write any new driver.
You jus
Hello Andreas,
Thanks for this explanation.
I will try to write my own driver for my board.
Best regards
alex
On 02/10/2011 07:24 PM, Andreas Pretzsch wrote:
> Am Donnerstag, den 10.02.2011, 17:04 +0100 schrieb Alexandre Gambier:
>> Dear Wolfgang,
>>
>> I tried to put some printk in the MTD dri
Am Donnerstag, den 10.02.2011, 17:04 +0100 schrieb Alexandre Gambier:
> Dear Wolfgang,
>
> I tried to put some printk in the MTD driver and it seems that the
> parse_mtd_partitions function is never called...
parse_mtd_partitions() is called from the mapping drivers. See e.g.
linux/drivers/mtd/m
Dear Wolfgang,
I tried to put some printk in the MTD driver and it seems that the
parse_mtd_partitions function is never called...
I will try to find what's wrong with my kernel configuration.
alex
On 02/10/2011 03:59 PM, Wolfgang Denk wrote:
> Dear Alexandre Gambier,
>
> In message<4d53f9fa.20
Dear Alexandre Gambier,
In message <4d53f9fa.2070...@ftemaximal.fr> you wrote:
>
> mtdids : nor0=NOR,nand0=NAND
...
> mtdparts=NOR:512k(U-Boot),128k(Environment),4M(Kernel),-(FreeNOR);NAND:32M(FS),-(FreeNAND)
...
> The problem is that once my system is running the MTD devices in /dev
> are not
Le 10/02/2011 15:45, Alexandre Gambier a écrit :
> Hello,
>
> I use U-Boot 1.3.1 with a NOR and a NAND Flash.
> I created the following partitions with U-Boot.
U-Boot 1.3.1 is rather old., BTW
> device nor0, # parts = 4
>#: namesizeoffset mask_flag
Hello,
I use U-Boot 1.3.1 with a NOR and a NAND Flash.
I created the following partitions with U-Boot.
device nor0 , # parts = 4
#: namesizeoffset mask_flags
0: U-Boot 0x0008 0x 0
1: Environment 0x000200
"Carlos kescuin" <[EMAIL PROTECTED]> wrote:
>
> I'm using a Coldfire m5329EVB and I would like to make some
> partitions (one for kernel and one for filsystem) on my NAND
> FLASH (16Mb). I've tryied to search the u-boot options
> (u-boo 2008.10) but it doesn't work at all.
>
> Does anybody kno
On Tue, Dec 09, 2008 at 06:09:08PM +0100, Carlos kescuin wrote:
> I'm using a Coldfire m5329EVB and I would like to make some partitions (one
> for kernel and one for filsystem) on my NAND FLASH (16Mb). I've tryied to
> search the u-boot options (u-boo 2008.10) but it doesn't work at all.
>
> Does
Hi,
I'm using a Coldfire m5329EVB and I would like to make some partitions (one
for kernel and one for filsystem) on my NAND FLASH (16Mb). I've tryied to
search the u-boot options (u-boo 2008.10) but it doesn't work at all.
Does anybody know the configure options or at least how to succeed in
par
19 matches
Mail list logo
