devf-ram, devf-file & devf-generic

Hi,

Can anybody explain what is a difference between them?
When should I use them and what is theirs application?

The ‘use devf-*’ command shows the same description for all of them.

Regards,
Jacek

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

Hi,

Can anybody explain what is a difference between them?
When should I use them and what is theirs application?

devf-generic is a “generic” flash driver that will auto-detect your
flash array for you, and figure out which MTD to use.

devf-ram is a flash driver framework that will use RAM to emulate
flash.

devf-file doesn’t seem to exist. If it did, I’d expect it to be
similar to devf-ram, but to use a file on another filesystem as the
storage to emulate flash, rather than by using RAM.

The ‘use devf-*’ command shows the same description for all of them.

I’d have to install the flash tdk and look, but this doesn’t entirely
surprise me. They’d have the same commandline options and everthing,
since they’re just variants on the same thing – a NOR flash driver.

(And, the use messages are supposed to be a short summary/reminder of
how to use something, not full documentation. Check the documentation
for full information on what something does, and what it’s intended to do.)

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

devf-generic is a “generic” flash driver that will auto-detect your
flash array for you, and figure out which MTD to use.

devf-ram is a flash driver framework that will use RAM to emulate
flash.

devf-file doesn’t seem to exist.

The devf-file exists :slight_smile:.

If it did, I’d expect it to be
similar to devf-ram, but to use a file on another filesystem as the
storage to emulate flash, rather than by using RAM.

Ok.

The ‘use devf-*’ command shows the same description for all of them.

I’d have to install the flash tdk and look, but this doesn’t entirely
surprise me. They’d have the same commandline options and everthing,
since they’re just variants on the same thing – a NOR flash driver.

(And, the use messages are supposed to be a short summary/reminder of
how to use something, not full documentation. Check the documentation
for full information on what something does, and what it’s intended to
do.)

The problem is that documentation doesn’t include any devf-file and
devf-generic description. Only the “devf-ram.html” file is included.

Also the “use devf-*” info is not so detailed. It prints the same lines for
devf-generic, devf-file and devf-ram except one thing - driver name.

Jacek


-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

devf-generic is a “generic” flash driver that will auto-detect your
flash array for you, and figure out which MTD to use.

devf-ram is a flash driver framework that will use RAM to emulate
flash.

devf-file doesn’t seem to exist.

The devf-file exists > :slight_smile:> .

Yeah, I found the source for it. It doesn’t seem to be
documented, though.

If it did, I’d expect it to be
similar to devf-ram, but to use a file on another filesystem as the
storage to emulate flash, rather than by using RAM.

Ok.

And, the source confirmed my guess.


The ‘use devf-*’ command shows the same description for all of them.

I’d have to install the flash tdk and look, but this doesn’t entirely
surprise me. They’d have the same commandline options and everthing,
since they’re just variants on the same thing – a NOR flash driver.

(And, the use messages are supposed to be a short summary/reminder of
how to use something, not full documentation. Check the documentation
for full information on what something does, and what it’s intended to
do.)

The problem is that documentation doesn’t include any devf-file and
devf-generic description. Only the “devf-ram.html” file is included.

Um… what version of the docs/OS do you have? Both 6.3.0 SP1 (current)
and 6.3.0 SP2 (next) have docs for about 15 different devf-* drivers,
including devf-ram and devf-generic.

Also the “use devf-*” info is not so detailed. It prints the same lines for
devf-generic, devf-file and devf-ram except one thing - driver name.

As I said, it isn’t supposed to be the detail, it is supposed to be a
quick summary/reminder of how to use a utility.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com

devf-file doesn’t seem to exist.

The devf-file exists > :slight_smile:> .

Yeah, I found the source for it. It doesn’t seem to be
documented, though.

Can you provide one example how to start devf-file driver?
I would like to see how it can be connected with file on another
filesystem.

Jacek Rudnicki <jacek.rudnicki@quantum.com.pl> wrote:

devf-file doesn’t seem to exist.

The devf-file exists > :slight_smile:> .

Yeah, I found the source for it. It doesn’t seem to be
documented, though.

Can you provide one example how to start devf-file driver?
I would like to see how it can be connected with file on another
filesystem.

You know about as much about running it as I do. (Actually, more,
as you have an executable to play with, and I don’t currently.)

It looks like it opens/O_CREAT a file in its CWD named fs1 (for the
first socket), so maybe if you ran it from different places in the
filesystem, it would use different filesystems for its “flash” file.

But, I’m just guessing.

-David

David Gibbs
QNX Training Services
dagibbs@qnx.com