* MTD+JFFS2 on DragonBall VZ
@ 2002-05-15 12:38 Ales Makarov
0 siblings, 0 replies; 4+ messages in thread
From: Ales Makarov @ 2002-05-15 12:38 UTC (permalink / raw)
To: Linux MTD mailing list
Hi,
I've got MTD+JFFS2 running on our board with Motorola DragonBall 68VZ328
CPU. We use CFI (or JEDEC) flashes (AMD/Fujitsu type: 29LV160, 29LV320).
I use cfi_probe (or modified jedec_probe) and physmap.c.
Till now I needed MTD with only one chip. But I want use MTD also on the
second chip (with partitioning). Do I have to write my own mapper for
our board?
Ales
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MTD+JFFS2 on DragonBall VZ
@ 2002-05-15 13:22 Jim Zeus
2002-05-16 9:09 ` Ales Makarov
0 siblings, 1 reply; 4+ messages in thread
From: Jim Zeus @ 2002-05-15 13:22 UTC (permalink / raw)
To: ales.makarov; +Cc: all in MTD mailinglist
--- Ales Makarov <ales.makarov@wolfhill.cz> wrote:
>Hi,
>>Till now I needed MTD with only one chip. But I want use MTD also on the
>second chip (with partitioning). Do I have to write my own mapper for
>our board?
You have to write your own mtd_partition structure
_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net
_____________________________________________________________
Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MTD+JFFS2 on DragonBall VZ
2002-05-15 13:22 MTD+JFFS2 on DragonBall VZ Jim Zeus
@ 2002-05-16 9:09 ` Ales Makarov
0 siblings, 0 replies; 4+ messages in thread
From: Ales Makarov @ 2002-05-16 9:09 UTC (permalink / raw)
To: zeusj; +Cc: Linux MTD mailing list
I've written my mtd_partition structure.
Should I add the mtd_device first and then mtd_partitions? (I don't need
the whole device access)
flash0_mtd->module = THIS_MODULE;
add_mtd_device(flash0_mtd);
add_mtd_partitions(flash0_mtd, flash0_parts, FLASH0_PARTS);
Ales
Jim Zeus wrote:
>
> --- Ales Makarov <ales.makarov@wolfhill.cz> wrote:
> >Hi,
> >>Till now I needed MTD with only one chip. But I want use MTD also on the
> >second chip (with partitioning). Do I have to write my own mapper for
> >our board?
>
> You have to write your own mtd_partition structure
>
> _____________________________________________________________
> Want a new web-based email account ? ---> http://www.firstlinux.net
>
> _____________________________________________________________
> Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: MTD+JFFS2 on DragonBall VZ
@ 2002-05-17 0:59 Jim Zeus
0 siblings, 0 replies; 4+ messages in thread
From: Jim Zeus @ 2002-05-17 0:59 UTC (permalink / raw)
To: ales.makarov, all in MTD mailinglist; +Cc: Ales Makarov
--- Ales Makarov <ales.makarov@wolfhill.cz> wrote:
>I've written my mtd_partition structure.
>
>Should I add the mtd_device first and then mtd_partitions? (I don't need
>the whole device access)
>
> flash0_mtd->module = THIS_MODULE;
> add_mtd_device(flash0_mtd);
> add_mtd_partitions(flash0_mtd, flash0_parts, FLASH0_PARTS);
>
NO ,I believe you need to add the mtd_partitions only.
Jim Zeus
_____________________________________________________________
Want a new web-based email account ? ---> http://www.firstlinux.net
_____________________________________________________________
Promote your group and strengthen ties to your members with email@yourgroup.org by Everyone.net http://www.everyone.net/?btn=tag
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-05-17 0:59 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-05-15 13:22 MTD+JFFS2 on DragonBall VZ Jim Zeus
2002-05-16 9:09 ` Ales Makarov
-- strict thread matches above, loose matches on Subject: below --
2002-05-17 0:59 Jim Zeus
2002-05-15 12:38 Ales Makarov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox