linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@austin.ibm.com>
To: Flavio Pereira <fpereira@azisa.com>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: MTD Driver (denx Linux 2.4.4)
Date: 31 Oct 2002 10:25:01 -0600	[thread overview]
Message-ID: <1036081502.1013.1299.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <1E354700654661418593A0D6B5A9D410089481@mail.azisa.co.za>


On Thu, 2002-10-31 at 08:37, Flavio Pereira wrote:
>
> I'm having difficulty in getting the MTD driver working. I'm using a
> non-CFI complaint Sharp chip so I have defined CONFIG_MTD_SHARP. However
> I cannot locate anywhere in the code where the kernel will call
> sharp_probe_init. In any case I forced init_mtd (mtdcore.c) to call
> sharp_probe_init and it seems to load the driver okay as I see the
> following on my serial console
>
> JFFS version 1.0, (C) 1999, 2000  Axis Communications AB
> JFFS2 version 2.1. (C) 2001 Red Hat, Inc., designed by Axis
> Communications AB.
> MTD Sharp chip driver <ds@lineo.com>
> MTD Sharp chip driver <ds@lineo.com>
>
> Now my question is, do I need to force this driver to load or am I
> missing some compile flag? How do I go about partitioning the flash, ie
> how does this driver link to a flash map?

Those "MTD" lines above, does that mean your driver is being initialized
twice?

Linux uses ELF tricks for initialization: addresses of all the functions
marked __init are put into their own ELF section, and common code
somewhere (I forget where) just loops over this section, calling each
init function in turn. So you should *not* add an explicit call to your
init routine.

-Hollis

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-10-31 16:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31 14:37 MTD Driver (denx Linux 2.4.4) Flavio Pereira
2002-10-31 16:25 ` Hollis Blanchard [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=1036081502.1013.1299.camel@granite.austin.ibm.com \
    --to=hollis@austin.ibm.com \
    --cc=fpereira@azisa.com \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).