All of lore.kernel.org
 help / color / mirror / Atom feed
From: Munira Ahmed <munira.ahmed@radixs.com>
To: Ralph Siemsen <ralphs@netwinder.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: do_map_probe and driver name
Date: Tue, 17 May 2005 09:33:37 +0800	[thread overview]
Message-ID: <1116293617.31694.54.camel@server11> (raw)
In-Reply-To: <42889844.60007@netwinder.org>


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.


On Mon, 2005-05-16 at 08:55 -0400, Ralph Siemsen wrote:
> Please don't post the same message to multiple mailing lists.
> 
> Munira Ahmed wrote:
> > 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/
> 
-- 
Munira Ahmed

      reply	other threads:[~2005-05-17  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  2:46 do_map_probe and driver name Munira Ahmed
2005-05-16 12:55 ` Ralph Siemsen
2005-05-17  1:33   ` Munira Ahmed [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1116293617.31694.54.camel@server11 \
    --to=munira.ahmed@radixs.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=ralphs@netwinder.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.