Skip to contentSkip to conversation

do_map_probe and driver name

DISCUSSION Munira Ahmed 2 participants 3 messages May 16, 2005 – May 17, 2005 Memory technology devices (MTD)

lore
Share & tools
lore

Munira Ahmed

author
#0 lore raw

do_map_probe requires name of a driver to probe.

Now how do I know the names of mtd drivers to see if I have them or not

How do I find out which driver is currently active

is there any list of all or some driver names.

Regards

Signature · 27 lines
Munira Ahmed
Senior Embedded Specialist

Radixs Pte Ltd
Email:[email protected]


Main: +65 6335 8600
Fax: +65 6335 8601
URL: www.radixs.com 

1 Temasek Avenue, #21-01, Millenia Tower, Singapore 039192

Disclaimer Notice: This email, its content and any files transmitted
with it are intended solely for the addressee(s) and may be confidential
and privileged. Any unauthorised disclosure or use or dissemination of
the information contained herein, either whole or partial, is
prohibited. Radixs Pte Ltd (Radixs) cannot accept liability for any
statements made which are clearly the sender's own and not expressly
made on behalf of Radixs or one of its agents. If you have received this
message in error, please notify the sender immediately, and delete this
email from your computer system. Radixs has taken reasonable precaution
to ensure no viruses are present in this email, however Radixs does not
accept responsibility for any loss or damage arising from the use of
this email or attachments.

Co. Reg. 200104892Z
#1 lore raw

Please don't post the same message to multiple mailing lists.

Quoted 4 lines · Munira Ahmed

do_map_probe requires name of a driver to probe.
Now how do I know the names of mtd drivers to see if I have them or not How do I find out which driver is currently active
is there any list of all or some driver names.

The answer can be found easily by searching for calls to do_map_probe in the kernel/drivers/mtd subdirectories. For example in physmap.c:

	static const char *rom_probe_types[] = {
		"cfi_probe", "jedec_probe", "map_rom", NULL
	};
	const char **type = rom_probe_types;

	for(; !mymtd && *type; type++) {
                mymtd = do_map_probe(*type, &physmap_map);
        }

So you can ee it is called with names like "cfi_probe" etc. These functions are defined drivers/mtd/chips directory. So take a look at the files in that directory to discover the names you seek.

-R

author
#2 lore raw

what's wrong in posting the same question to two different lists?

I just wanted to be able to reach more people.

Thanks for your guidance. I will keep that in mind now on.

Quoted 30 lines · Ralph Siemsen

Please don't post the same message to multiple mailing lists.

Quoted 4 lines · Munira Ahmed

do_map_probe requires name of a driver to probe.
Now how do I know the names of mtd drivers to see if I have them or not How do I find out which driver is currently active
is there any list of all or some driver names.

The answer can be found easily by searching for calls to do_map_probe in the kernel/drivers/mtd subdirectories. For example in physmap.c:

	static const char *rom_probe_types[] = {
		"cfi_probe", "jedec_probe", "map_rom", NULL
	};
	const char **type = rom_probe_types;

	for(; !mymtd && *type; type++) {
                 mymtd = do_map_probe(*type, &physmap_map);
         }

So you can ee it is called with names like "cfi_probe" etc. These functions are defined drivers/mtd/chips directory. So take a look at the files in that directory to discover the names you seek.

-R

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

Signature · 1 line
Munira Ahmed