From: Xavier DEBREUIL <xde@inventel.fr>
To: linux-mtd@lists.infradead.org
Subject: use of low level driver
Date: Tue, 19 Jun 2001 10:29:48 +0200 [thread overview]
Message-ID: <3B2F0D7C.AEB02B3E@inventel.fr> (raw)
I am a little confused about the use of low level functions provided by
different drivers.
I got the mtd stuff work on my board with amd std non cfi flashes. In
amd_flash.c
int __init amd_flash_init(void)
{
register_mtd_chip_driver(&amd_flash_chipdrv);
return 0;
}
allows me to call : do_map_probe("amd_flash",...)
But, if I want to call do_map_probe("cfi" or "cfi_intel",...), I need to
have registered the corresponding mtd chip driver. But when it is part
of the kernel (not a module), "mod_init_t cfi_intelext_init(void)" is
not called in kernel initialisation ? (correct?)
Is it correct to replace it with
int __init cfi_intelext_init(void)
{
register_mtd_chip_driver(&cfi_intelext_chipdrv);
return 0;
}
and
mod_init_t cfi_probe_init(void) by
int __init cfi_probe_init(void)
so that I will be able to call do_map_probe("cfi_intel" or "cfi",...) in
kernel initialisation ?
otherwise, what happend is that kmod is looking for module in the
filesystem ; but at that point, no root fs is mounted.
Xavier
next reply other threads:[~2001-06-19 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 8:29 Xavier DEBREUIL [this message]
2001-06-19 8:40 ` use of low level driver David Woodhouse
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=3B2F0D7C.AEB02B3E@inventel.fr \
--to=xde@inventel.fr \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox